Presify service status
Live status and 90-day history, refreshed every five minutes. Incident notes are posted here as they happen.
Components
- Operational
- Degraded
- Outage
- Unknown
- No data
Presence collection
Reading Teams presence and building timelines
Web app & sign-in
The Presify dashboard and API
Report generation
Excel and CSV exports
Email notifications
Alerts, digests, and billing email
Microsoft connectivity
Presify’s connection to Microsoft Graph
Hover a strip, or focus it and use the arrow keys, to read any day. Home and End jump to the ends.
Incidents
Update times in UTCWhen something affects the service, the incident and each update are posted here, newest first.
Status reflects the production service. Questions? Contact us.
How to read this page.
Each component is checked every five minutes, and each cell is one UTC day. The banner at the top says one of five things:
Any degraded time, or a single down sample (about five minutes), turns a day amber. A day turns red only with two or more down samples, about ten minutes or more. A short blip never paints a whole day red.
From the samples in the last 20 minutes, three or four of them. A component shows Outage only when its newest two samples are both down. Any down or degraded sample in that window shows Degraded until it ages out. An open incident posted for a component also shows it as Degraded until the incident is resolved.
If the last status sample is more than 15 minutes old, the banner says the data is delayed and current states show as unknown. The page never keeps showing green on old data.
No status samples were recorded for that day, for example before history began for a component. It is not the same as an outage.
No. It reports on the shared production service only. It never shows customer names, tenant data or presence data.
Try Presify on your own Teams presence.
One read-only Microsoft sign-in, about five minutes, nothing installed. History starts building from the moment you connect.