ACCC UpReport
Report a service outage
UpReport generated on Oct 11, 2008 4:11 am
| Service | Status | Since |
|---|---|---|
| ADSM | Up | 09/16 13:22 |
| Argo | Up | 01/30 13:49 |
| Argo-New | Up | 10/09 01:06 |
| BlackBoard | Up | 07/27 20:01 |
| Exchange | Up | 10/08 20:03 |
| Helpdesk(rt) | Partial Service | 10/11 04:03 |
| Icarus | Up | 10/03 14:48 |
| LIB-UICCAT | Up | 07/17 11:49 |
| Labs | Up | 10/09 07:29 |
| Keyserv | Up | 09/27 10:49 |
| LDAP | Up | 09/18 09:37 |
| Listserv | Up | 05/03 07:36 |
| Mailserv | Up | 12/12 08:51 |
| Notes | Up | 10/04 23:23 |
| Pharos | Up | 09/11 03:04 |
| RealServer | Up | 03/07 18:29 |
| Smtpserv | Up | 03/05 17:28 |
| Tigger | Up | 06/08 10:51 |
| UICalendar | Up | 09/18 17:05 |
| Web | Up | 06/08 10:51 |
| Webmail | Up | 09/02 14:09 |
Service Alerts
No service alerts at this time.
News
No announcements at this time.
Reporting service outages
If you have trouble. If the outage appears on the UpReport, and particularly if there are any news items about it, then we are already aware and you don't need to report it. If you do need to report a problem:
- Emergencies: 312-413-8080
- Non-emergencies: Contact the CSO at consult@uic.edu or 312-413-0003.
- Other contacts: HELP, which is also available on the HELP button on the top banner of most ACCC pages.
Also Note:
- Services are checked typically several times/hour. So in most cases, we will detect the problem before you do. Our internal reporting system checks these systems and others, in greater detail, and will escalate reports as needed. Of course, individuals might have problems that are not reflected in the health of the overall service.
- Occasionally a monitor will report a false positive (meaning the service is really up, but the monitor reports it down.) Usually this is because a service gets temporarily busy and fails to respond within a timeout period. So it looks like it is down to the monitor, but it recovers on its own. Mail delivery is the most likely candidate for false positives, but other services can show this, too.
- One ramificaton of false positives is that even when a service is up, the "Since" time may be much shorter than the true time the service has been available. So use the times as a guide, but realize that services are typically more reliable than shown.
- False negatives (when the service is down but the monitor reports it up) are quite rare, other than the minutes between when a service fails and when the monitor next checks. This would mean the monitor is not checking all the right things. False negatives become even rarer as we improve the monitoring.
- Some services (e.g. "tigger") are monitored in several ways, and it's quite possible that tigger as a whole is up, but individual services on tigger are down. Click on the status link to see details.