DiscordStatus record
Latest recorded vendor status
Source checked
A recorded report, not a live test of your application.
Open official status pageCheck the product, region and time against your own logs.
Check counts and incident historyComponent records
Vendor products and regions, with issue records listed first.
| Product / region | Recorded status | Record last seen |
|---|---|---|
Sydney | Operational | |
Tax Calculation Service | Operational | |
Third-party | Operational | |
US Central | Operational | |
US East | Operational | |
US South | Operational | |
US West | Operational | |
Voice | Operational | |
Web | Operational |
- Operational
Sydney
Record last seen - Operational
Tax Calculation Service
Record last seen - Operational
Third-party
Record last seen - Operational
US Central
Record last seen - Operational
US East
Record last seen - Operational
US South
Record last seen - Operational
US West
Record last seen - Operational
Voice
Record last seen - Operational
Web
Record last seen
25 to 33 of 33 components
“Last seen” is saved when a component changes or its record is refreshed. It is not the time of every status check. These records can differ from the vendor’s overall report.
Recent incidents
Past 30 days
Started or first observed in this window. A record may close when a post disappears or our tracking period expires; this does not confirm recovery. A missing closure time does not confirm an ongoing outage.
Elevated API error rate
Started
Closed in record
Age group status mismatch across devices
Started
Closed in record
Issue / Delay in establishing call connection
Started
Closed in record
Recorded impact: Major
Read vendor reportIssue establishing voice call
Started
Closed in record
Recorded impact: Major
Read vendor report
Maintenance and future scheduled work are excluded.
Explore reliability history