Plan requirement
| Subscription | Any plan |
| Access | Agent |
Check the pluscloud status page first to see whether Zendesk is down. It shows the current status per component, plus any planned maintenance.
Start with our status page
status.pluscloud.nl/en/zendesk breaks Zendesk down the way an incident actually arrives: Support, Knowledge, AI Agents, Chat, Voice, Analytics, Sunshine Platform, Sunshine Conversations, Contact Center and Services, each with its own state. Planned maintenance is on the same page, which answers the second question people have when something is slow on a Tuesday morning.
The page updates itself, so what you read is what we are looking at. If you run Wildix as well, or you are not yet sure which part of your setup is misbehaving, status.pluscloud.nl/en covers everything we deliver on one page, CLASSOUND and Multi Carrier Trunks and the integrations included.
The source at Zendesk itself
Zendesk publishes its own page at status.zendesk.com, and it is worth opening when you want the detail behind a confirmed incident. It asks for your subdomain first, because accounts run on different infrastructure and an incident hits some and not others. See Monitoring your account on the Zendesk status page for finding your pod and reading the page properly.
Neither page is proof. Small or regional problems are not always posted, and a post can lag what you are experiencing by a while. A green page means nothing is known, not that nothing is wrong.
What to check yourself
If both pages are clear, a few checks separate a platform problem from one of your own.
- One person or everybody. If the colleague at the next desk has no trouble, the cause sits on the affected machine or account rather than at Zendesk.
- A private window or another browser. This rules out an extension, a stale session or a cached file in one go, and it takes less time than describing the symptom.
- Your network. A firewall or proxy that has started filtering something is a common cause of a slowness that looks like an outage. See Configuring your firewall for Zendesk.
- One channel or all of them. Email arriving but voice failing points at a single component, and that is exactly what the status page splits out.
Telling us
Report it to pluscloud support rather than waiting for the status page to catch up. What helps most: your subdomain, the time it started, whether it is one agent or the whole team, and one ticket number where you can see it going wrong. We can see more of your environment than a status page can, and where the cause is at Zendesk we take it up from our side.
During a confirmed incident, telling your own customers that there is a platform problem is better than an unexplained delay. People accept an outage far more readily than silence.
Comments
0 comments
Article is closed for comments.