Our Telephony Engineers will be performing maintenance on our Inbound SIP proxy servers in the Australia region. This maintenance will not disrupt service, but you may notice re-registration of your devices during the maintenance, as our primary and secondary SIP IP addresses are moved between hosts. Posted on
Jul 26, 2024 - 13:25 UTC
Resolved -
This incident has been resolved.
Jul 26, 21:52 UTC
Monitoring -
A core network fix has been implemented and we are monitoring the results.
Jul 22, 05:53 UTC
Investigating -
We are currently investigating this issue. We advice all customers using Expeto IMSI to select either Automatic IMSI selection or Sparkle IMSI to ensure service continuity (or restoration in case of service had been lost).
Jul 19, 13:44 UTC
Resolved -
This incident has been resolved.
Jul 26, 21:45 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
Jul 25, 20:40 UTC
Identified -
Countries affected by this incident: Comoros Sao Tome and Principe South Sudan Canada Colombia Peru Bulgaria Cyprus Finland Czech Republic Finland Germany Korea (the Republic of) Portugal Saudi Arabia Slovakia Spain Slovakia Morocco Qatar Yemen Saint Pierre and Miquelon Northern Mariana Islands Solomon Islands Vanuatu Taiwan Switzerland Turkmenistan
Jul 25, 19:01 UTC
Completed -
The scheduled maintenance has been completed.
Jul 26, 12:59 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 26, 10:00 UTC
Scheduled -
Our Telephony Engineers will be performing maintenance on our Inbound SIP proxy servers in the Canada region. This maintenance will not disrupt service, but you may notice re-registration of your devices during the maintenance, as our primary and secondary SIP IP addresses are moved between hosts.
Jul 25, 16:50 UTC
Completed -
The scheduled maintenance has been completed.
Jul 24, 23:59 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 24, 10:00 UTC
Scheduled -
Our Telephony Engineers will be performing maintenance on our Inbound SIP proxy servers in the US region. This maintenance will not disrupt service, but you may notice re-registration of your devices during the maintenance, as our primary and secondary SIP IP addresses are moved between hosts.
Jul 23, 18:06 UTC
Completed -
The scheduled maintenance has been completed.
Jul 24, 13:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 24, 12:00 UTC
Scheduled -
The Wireless team is performing a maintenance window to route traffic to the new 3G infrastructure components. The maintenance window will last for one hour, with no service disruption to be expected. Maintenance schedule to begin 12PM UTC 24th July 2024
Jul 23, 16:26 UTC
Completed -
The scheduled maintenance has been completed.
Jul 17, 23:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 17, 16:00 UTC
Scheduled -
Our downstream vendor will be conducting maintenance on their services.
During this time, number searching and ordering may be disrupted in the following countries: Italy, Switzerland, Norway, Sweden, Denmark, Luxembourg, Portugal
Jul 9, 16:51 UTC
Resolved -
This incident has been resolved.
Jul 17, 22:30 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
Jul 16, 20:43 UTC
Update -
We are currently investigating an issue where a subset of inbound multipart messages are failing to deliver towards Telnyx long codes.
This is happening only for US / CAN (+1) numbers.
Jul 16, 18:25 UTC
Investigating -
We are currently investigating an issue where a subset of inbound multipart messages are failing to deliver towards Telnyx long codes.
Jul 16, 18:24 UTC
Resolved -
This incident has been resolved. IMPACT: SMS message latency from 8:45 a.m. CT to 4:05 p.m. CT.
Jul 15, 08:07 UTC
Identified -
You may experience messaging delays between Telnyx long codes and external short codes , both inbound and outbound messages may experience delays. This issue is on the downstream side. Another update will be provided as soon as more information becomes available.
Jul 12, 18:04 UTC