Network Status
Track service availability, maintenance notices and incident communication so you can respond faster when customer-facing systems are affected.
- Use this page first when multiple clients or domains appear affected.
- Planned maintenance should be checked before troubleshooting normal behavior changes.
- Incident communication improves coordination for support and operations teams.
At a glance
Service Blocks & Key Capabilities
Current Incidents
Check if the issue is already known and under response.
Maintenance Windows
Review planned changes that may affect service behavior.
Resolved Events
See what happened and what was done about it.
What You Should Know
What Status Updates Cover
Status updates may include active outages, degraded behavior, maintenance windows, upstream dependencies and resolution confirmation.
- Current service-impacting incidents.
- Planned maintenance notices.
- Resolved event communication.
How To Use Status Data
When an incident is listed, use that context to avoid duplicate troubleshooting and instead focus on business continuity steps, customer communication and escalation where needed.
- Check for platform-wide incidents first.
- Use timestamps to compare with your issue.
- Escalate only when your case differs materially from the posted event.
Operational Value
Transparent status communication reduces uncertainty for client teams and helps support interactions move faster with shared context.
- Better client communication during downtime.
- Reduced duplicate incident reports.
- Clearer escalation handling.
Related Pages & Next Actions
Frequently Asked Questions
Should I still submit a ticket if status looks normal?
Yes. If your service is affected and there is no related incident posted, open a support request with exact details.
Need direct incident support after checking status?
If the issue is isolated to your account or materially different from a posted event, send the exact details to support for diagnosis.