System status
Current state of the Solved Telephony network, from carrier interconnects through to the portal. Maintained by the engineers who run the routes.
Component status
Twelve components, from the carrier edge to the screens you sign in to.
-
Operational
Voice origination
Inbound calls from the PSTN to your trunks, DIDs, and endpoints.
-
Operational
Voice termination
Outbound calls from your trunks to carrier destinations.
-
Operational
SIP registration
Registrar and IP authentication for trunks, softswitches, and devices.
-
Operational
Number provisioning
DID search, reservation, purchase, assignment, and release.
-
Operational
Porting
LOA intake, port submission, FOC scheduling, and port status updates.
-
Operational
Messaging (SMS/MMS)
Long-code and toll-free send and receive, plus delivery receipts.
-
Operational
Call recording
Network-side capture, storage, and playback or download of media.
-
Operational
Transcription
Speech to text on recordings, with redaction, summary, and sentiment.
-
Operational
Programmable routing
Campaigns, buyers, publishers, bidding, caps, queues, and IVR.
-
Operational
AI Voice Agents
Agent sessions, media handling, and transfer to a human.
-
Operational
API
REST endpoints, webhook delivery, and scheduled CDR export.
-
Operational
Portal
Account sign-in, configuration screens, and usage reporting.
Voice components cover the shared network. If you run on dedicated trunks or a dedicated route set, your account contact will tell you directly when something on your own path changes.
Scheduled maintenance
No maintenance is scheduled. When work is planned, it is announced here and by email at least 72 hours in advance.
- The window. 02:00 to 05:00 Eastern, the quietest span for United States calling traffic.
- Call paths first. Work that can touch live call paths is done one carrier or one media group at a time, with the rest of the rotation carrying traffic.
- Campaign peaks. Tell us your peak weeks and we will not schedule optional work inside them.
- Emergency changes. Security fixes and carrier-side failures can move without notice. Those are announced as incidents, not maintenance.
Operating targets
- 99.99%
- Availability target for voice origination and termination.
- under 2s
- Post-dial delay target on primary routes.
- 72 hours
- Minimum notice before planned maintenance.
- 60 minutes
- Maximum gap between updates while an incident is open.
How we tell you
Three channels, in the order you will normally hear about something. Escalations end with us, because we hold the carrier relationships rather than passing them to a provider above us.
Shared support channel
Platform customers get a Slack or Teams channel with the engineers who run the routes. Incidents are posted there first, usually before this page changes.
Email notices
To subscribe, send the addresses you want on the list to contact@solvedtele.com. You will get incident notices and maintenance notices, nothing else.
This page
Updated by hand during an incident, then left showing the resolution note until the next change. Bookmark solvedtele.com/status.
Reporting a problem we have not posted
Bring these four things and the first reply can contain an answer instead of a question.
Call ID
The SIP Call-ID or our call identifier from the CDR. One identifier is enough to pull the full trace.
Timestamp
Time and time zone, or a UTC timestamp. A five-minute window is fine.
Destination
The dialed number or the DID that received the call, and the trunk or sub-account it ran on.
Symptom
What you heard or saw: fast busy, dead air, one-way audio, a specific SIP response code, a failed API call.
Email contact@solvedtele.com or call +1 (866) 415-6192. For anything security related, see the security page.
FAQs
Status questions
How is this page updated?
By hand. An engineer changes the status of the affected component here and publishes the page, so what you read is a statement from the people running the network rather than the output of a probe. Incidents are posted to your shared support channel at the same time.
How often will I hear from you during an incident?
At least every 60 minutes while an incident is open, even when the update is that we are still working. The final note names the affected components, the window, and what we changed.
How do I subscribe to status updates?
Email contact@solvedtele.com with the addresses you want on the list. Platform customers also get incident notices in the shared Slack or Teams channel opened during onboarding, which is the fastest path.
When does planned maintenance happen?
In a window between 02:00 and 05:00 Eastern, announced at least 72 hours in advance. Work that can affect live call paths is scheduled outside United States calling hours, and we do not schedule optional maintenance during a customer campaign peak if you tell us about it.
Something is broken but this page says operational. What now?
Tell us rather than waiting for the page to catch up. Email contact@solvedtele.com or call +1 (866) 415-6192 with a call ID, a timestamp, and the destination, and we can pull the SIP trace for that leg.
Something else? Contact us
Seeing something this page is not?
Send a call ID and a timestamp and we will pull the SIP trace for that leg.