Outage in Call2Teams
Failing Calls and Registrations
Resolved Minor
December 20, 2023 - Started about 2 years ago
- Lasted about 16 hours
Incident Report
A High CPU issue on the serving SBC aeuwa08 20.126.150.164/32 caused a failover to the secondary SBC aeuwf08 40.69.2.153/32.
This is standard policy in this issue
A routing issue, which was the cause of the call failures, requires further testing. We have addressed the High CPU issue so feel confident that this will not trigger the issue again.
Components affected
Call2Teams SBCs - EuropeNeed to monitor Call2Teams outages?
- Monitor all your external dependencies in one place
- Get instant alerts when outages are detected
- Be the first to know if service is down
- Show real-time status on private or public status page
- Keep your team informed
Latest Call2Teams outages
Delay in Domain Propagation Affecting Account Setups - almost 2 years ago
Test - Not real incident - almost 2 years ago
major Microsoft outage - almost 2 years ago
Inbound Call failures to MSTEAMS - almost 2 years ago
The Status Page Aggregator with Early Outage Detection
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 5450 services available
Integrations with
