Twilio

Components

• Account Insights
  Operational
• ACCOUNT SECURITY
  Operational
• API v2
  Operational
• API v3
  Operational
• Billing
  Operational
• Client Mobile IE1
  Operational
• Client Web IE1
  Operational
• Console
  Operational
• Customer Support Center
  Operational
• Debugger & Alarms
  Operational
• Dedicated IP Address
  Operational
• DEVELOPER TOOLS
  Operational
• Event Webhooks
  Operational
• Messaging Services
  Operational
• Notify
  Operational
• Organization
  Operational
• Origination IE1
  Operational
• REST API
  Operational
• SendGrid API
  Operational
• SMS
  Operational
• SMS, Europe
  Operational
• Termination IE1
  Operational
• TWILIO PLATFORM
  Operational
• Webhooks
  Operational
• WhatsApp Messaging
  Operational

Scheduled Maintenance

• Russia SMS Carrier Maintenance - Tele2

  Twilio · Updated 3 days ago

• Czech Republic SMS Carrier Maintenance - T-Mobile

  Twilio · Updated 1 day ago

Recent incidents

1. France SMS Carrier Maintenance - SFR

   Maintenance · 5 Nov 2026, 05:00 · resolved about 5 hours ago

   • resolved5 Nov, 08:01

     The scheduled maintenance window ended at 5 Nov 2026, 08:00. Closed automatically by the status page.

   • monitoring5 Nov, 05:02

     **2026-10-26T15:14:11.402Z** — <p>The SFR network in France is conducting a planned maintenance from 04 November 2026 at 21:00 PST until 05 November 2026 at 00:00 PST. During the maintenance window, there could be intermittent delays delivering SMS to SFR France handsets.</p> **2026-11-05T04:00:21.195Z** — Maintenance will begin as scheduled in 60 minutes. **2026-11-05T05:00:07.426Z** — Scheduled maintenance is currently in progress. We will provide updates as necessary.

   • identified5 Nov, 04:00

     **2026-10-26T15:14:11.402Z** — <p>The SFR network in France is conducting a planned maintenance from 04 November 2026 at 21:00 PST until 05 November 2026 at 00:00 PST. During the maintenance window, there could be intermittent delays delivering SMS to SFR France handsets.</p> **2026-11-05T04:00:21.195Z** — Maintenance will begin as scheduled in 60 minutes.

   • identified26 Oct, 15:16

     **2026-10-26T15:14:11.402Z** — <p>The SFR network in France is conducting a planned maintenance from 04 November 2026 at 21:00 PST until 05 November 2026 at 00:00 PST. During the maintenance window, there could be intermittent delays delivering SMS to SFR France handsets.</p>

2. Mail Settings Maintenance

   Maintenance · 4 Nov 2026, 22:00 · resolved about 13 hours ago

   • resolved5 Nov, 00:00

     The scheduled maintenance window ended at 5 Nov 2026, 00:00. Closed automatically by the status page.

   • monitoring4 Nov, 22:00

     **2026-10-26T23:45:41.847Z** — In order to increase the stability and scalability of our systems, we are performing maintenance on our infrastructure on November 4, 2026 from 14:00 until 16:00 PST. During this time customers may be temporarily unable to manage Mail Settings (Address Allow List, Bounce Purge, Event Notification, Footer, Forward Bounce, Forward Spam or Legacy Email Template) or related Tracking Settings, Event Webhook and Inbound Parse settings. Reading existing settings will function as normally. This maintenance does not impact mail send. Thank you for your patience through this maintenance. **2026-11-04T21:01:27.278Z** — Maintenance will begin as scheduled in 60 minutes. **2026-11-04T22:00:10.128Z** — Scheduled maintenance is currently in progress. We will provide updates as necessary.

   • identified4 Nov, 21:02

     **2026-10-26T23:45:41.847Z** — In order to increase the stability and scalability of our systems, we are performing maintenance on our infrastructure on November 4, 2026 from 14:00 until 16:00 PST. During this time customers may be temporarily unable to manage Mail Settings (Address Allow List, Bounce Purge, Event Notification, Footer, Forward Bounce, Forward Spam or Legacy Email Template) or related Tracking Settings, Event Webhook and Inbound Parse settings. Reading existing settings will function as normally. This maintenance does not impact mail send. Thank you for your patience through this maintenance. **2026-11-04T21:01:27.278Z** — Maintenance will begin as scheduled in 60 minutes.

   • identified26 Oct, 23:46

     **2026-10-26T23:45:41.847Z** — In order to increase the stability and scalability of our systems, we are performing maintenance on our infrastructure on November 4, 2026 from 14:00 until 16:00 PST. During this time customers may be temporarily unable to manage Mail Settings (Address Allow List, Bounce Purge, Event Notification, Footer, Forward Bounce, Forward Spam or Legacy Email Template) or related Tracking Settings, Event Webhook and Inbound Parse settings. Reading existing settings will function as normally. This maintenance does not impact mail send. Thank you for your patience through this maintenance.

3. Russia SMS Carrier Maintenance - Tele2

   Maintenance · 4 Nov 2026, 20:00 · resolved about 11 hours ago

   • resolved5 Nov, 02:00

     The scheduled maintenance window ended at 5 Nov 2026, 02:00. Closed automatically by the status page.

   • monitoring4 Nov, 20:00

     **2026-11-03T10:41:07.316Z** — <p>The Tele2 network in Russia is conducting a planned maintenance from 04 November 2026 at 12:00 PST until 04 November 2026 at 18:00 PST. During the maintenance window, there could be intermittent delays delivering SMS to Tele2 Belgium handsets.</p> **2026-11-04T19:00:35.577Z** — Maintenance will begin as scheduled in 60 minutes. **2026-11-04T20:00:08.217Z** — Scheduled maintenance is currently in progress. We will provide updates as necessary.

   • identified4 Nov, 19:02

     **2026-11-03T10:41:07.316Z** — <p>The Tele2 network in Russia is conducting a planned maintenance from 04 November 2026 at 12:00 PST until 04 November 2026 at 18:00 PST. During the maintenance window, there could be intermittent delays delivering SMS to Tele2 Belgium handsets.</p> **2026-11-04T19:00:35.577Z** — Maintenance will begin as scheduled in 60 minutes.

   • identified3 Nov, 10:42

     **2026-11-03T10:41:07.316Z** — <p>The Tele2 network in Russia is conducting a planned maintenance from 04 November 2026 at 12:00 PST until 04 November 2026 at 18:00 PST. During the maintenance window, there could be intermittent delays delivering SMS to Tele2 Belgium handsets.</p>

4. SMS Delivery Delays from Twilio to Lycamobile United Kingdom

   Minor · 3 Nov 2026, 03:07 · resolved 2 days ago

   • resolved3 Nov, 05:49

     Auto-resolved by the status page: the vendor stopped reporting this incident in their feed.

   • monitoring3 Nov, 03:47

     **2026-11-03T03:07:58.945Z** — Twilio customers may be experiencing SMS delivery delays from Twilio to Lycamobile network subscribers in the United Kingdom. Our team is actively investigating this issue. We will provide another update in 1 hour or as soon as more information becomes available. **2026-11-03T03:09:51.844Z** — Twilio customers may be experiencing SMS delivery delays from Twilio to Lycamobile network subscribers in the United Kingdom. Our team has identified the cause, and is working to resolve the issue. We will provide another update in 1 hour or as soon as more information becomes available. **2026-11-03T03:45:59.830Z** — We have observed a recovery in SMS delivery from Twilio to Lycamobile network subscribers in the United Kingdom and are monitoring service stability. We will provide another update in 2 hours or as soon as more information becomes available.

   • identified3 Nov, 03:24

     **2026-11-03T03:07:58.945Z** — Twilio customers may be experiencing SMS delivery delays from Twilio to Lycamobile network subscribers in the United Kingdom. Our team is actively investigating this issue. We will provide another update in 1 hour or as soon as more information becomes available. **2026-11-03T03:09:51.844Z** — Twilio customers may be experiencing SMS delivery delays from Twilio to Lycamobile network subscribers in the United Kingdom. Our team has identified the cause, and is working to resolve the issue. We will provide another update in 1 hour or as soon as more information becomes available.

   • investigating3 Nov, 03:22

     **2026-11-03T03:07:58.945Z** — Twilio customers may be experiencing SMS delivery delays from Twilio to Lycamobile network subscribers in the United Kingdom. Our team is actively investigating this issue. We will provide another update in 1 hour or as soon as more information becomes available.

   • identified3 Nov, 03:12

     **2026-11-03T03:07:58.945Z** — Twilio customers may be experiencing SMS delivery delays from Twilio to Lycamobile network subscribers in the United Kingdom. Our team is actively investigating this issue. We will provide another update in 1 hour or as soon as more information becomes available. **2026-11-03T03:09:51.844Z** — Twilio customers may be experiencing SMS delivery delays from Twilio to Lycamobile network subscribers in the United Kingdom. Our team has identified the cause, and is working to resolve the issue. We will provide another update in 1 hour or as soon as more information becomes available.

   • investigating3 Nov, 03:08

     **2026-11-03T03:07:58.945Z** — Twilio customers may be experiencing SMS delivery delays from Twilio to Lycamobile network subscribers in the United Kingdom. Our team is actively investigating this issue. We will provide another update in 1 hour or as soon as more information becomes available.

5. Russia SMS Carrier Maintenance - MTS

   Maintenance · 3 Nov 2026, 03:00 · resolved 2 days ago

   • resolved3 Nov, 04:00

     The scheduled maintenance window ended at 3 Nov 2026, 04:00. Closed automatically by the status page.

   • monitoring3 Nov, 03:02

     **2026-11-02T21:05:23.809Z** — <p>The MTS network in Russia is conducting a planned maintenance from 02 November 2026 at 19:00 PST until 02 November 2026 at 20:00 PST. During the maintenance window, there could be intermittent delays delivering SMS to MTS Belarus handsets.<br><br>We are aware of the short notice and are working with our Carrier Partners to provide earlier notification where possible.</p> **2026-11-03T02:00:36.364Z** — Maintenance will begin as scheduled in 60 minutes. **2026-11-03T03:01:07.627Z** — Scheduled maintenance is currently in progress. We will provide updates as necessary.

   • identified3 Nov, 02:02

     **2026-11-02T21:05:23.809Z** — <p>The MTS network in Russia is conducting a planned maintenance from 02 November 2026 at 19:00 PST until 02 November 2026 at 20:00 PST. During the maintenance window, there could be intermittent delays delivering SMS to MTS Belarus handsets.<br><br>We are aware of the short notice and are working with our Carrier Partners to provide earlier notification where possible.</p> **2026-11-03T02:00:36.364Z** — Maintenance will begin as scheduled in 60 minutes.

   • identified2 Nov, 21:06

     **2026-11-02T21:05:23.809Z** — <p>The MTS network in Russia is conducting a planned maintenance from 02 November 2026 at 19:00 PST until 02 November 2026 at 20:00 PST. During the maintenance window, there could be intermittent delays delivering SMS to MTS Belarus handsets.<br><br>We are aware of the short notice and are working with our Carrier Partners to provide earlier notification where possible.</p>

6. RateQueue Host Down Did Not Recover

   Minor · 3 Nov 2026, 02:14 · resolved about 19 hours ago

   • resolved4 Nov, 18:10

     Auto-resolved by the status page: the vendor stopped reporting this incident in their feed.

   • monitoring4 Nov, 16:14

     **2026-11-03T02:14:03.275Z** — We are investigating delays in messages presented, while no messages are lost. We expect to provide another update in 1 hour or as soon as more information becomes available **2026-11-03T02:50:08.834Z** — Our engineering team has identified and mitigated the issue causing delays in messages which were presented, while no messages were lost we continue to investigate the root cause. We expect to provide another update in 1 hour or as soon as more information becomes available **2026-11-03T04:53:46.056Z** — Our engineering team has identified and mitigated the issue causing delays in messages which were presented, while no messages were lost we continue to investigate the root cause. We expect to provide another update in 2 hour or as soon as more information becomes available **2026-11-03T06:55:32.255Z** — Our engineering team has identified and mitigated the issue causing delays in messages which were presented, while no messages were lost we continue to investigate the root cause. We expect to provide another update in 4 hour or as soon as more information becomes available. **2026-11-03T10:51:38.882Z** — Our engineering team has identified and mitigated the issue causing delays in messages which were presented, while no messages were lost we continue to investigate the root cause. We expect to provide another update in 8 hours or as soon as more information becomes available. **2026-11-03T19:13:31.030Z** — The message delays were caused by an issue with a single host and affected only a portion of SMS traffic for approximately one hour. Service was restored and has been stable since with no data loss. We have applied a preventive measure to avoid a recurrence and are validating a permanent fix. We will share our next update in 8 hours or as soon as new information is available. **2026-11-04T03:47:16.214Z** — The message delays were caused by an issue with a single host and affected only a portion of SMS traffic for approximately one hour. Service was restored and has been stable since with no data loss. We have applied a preventive measure to avoid a recurrence and are validating a permanent fix. We will share our next update in 16 hours or as soon as new information is available. **2026-11-04T16:13:36.356Z** — Messaging is operating normally. We will continue to monitor for system stability. We'll provide another update in 2 hours or as soon as more information becomes available.

   • identified4 Nov, 03:48

     **2026-11-03T02:14:03.275Z** — We are investigating delays in messages presented, while no messages are lost. We expect to provide another update in 1 hour or as soon as more information becomes available **2026-11-03T02:50:08.834Z** — Our engineering team has identified and mitigated the issue causing delays in messages which were presented, while no messages were lost we continue to investigate the root cause. We expect to provide another update in 1 hour or as soon as more information becomes available **2026-11-03T04:53:46.056Z** — Our engineering team has identified and mitigated the issue causing delays in messages which were presented, while no messages were lost we continue to investigate the root cause. We expect to provide another update in 2 hour or as soon as more information becomes available **2026-11-03T06:55:32.255Z** — Our engineering team has identified and mitigated the issue causing delays in messages which were presented, while no messages were lost we continue to investigate the root cause. We expect to provide another update in 4 hour or as soon as more information becomes available. **2026-11-03T10:51:38.882Z** — Our engineering team has identified and mitigated the issue causing delays in messages which were presented, while no messages were lost we continue to investigate the root cause. We expect to provide another update in 8 hours or as soon as more information becomes available. **2026-11-03T19:13:31.030Z** — The message delays were caused by an issue with a single host and affected only a portion of SMS traffic for approximately one hour. Service was restored and has been stable since with no data loss. We have applied a preventive measure to avoid a recurrence and are validating a permanent fix. We will share our next update in 8 hours or as soon as new information is available. **2026-11-04T03:47:16.214Z** — The message delays were caused by an issue with a single host and affected only a portion of SMS traffic for approximately one hour. Service was restored and has been stable since with no data loss. We have applied a preventive measure to avoid a recurrence and are validating a permanent fix. We will share our next update in 16 hours or as soon as new information is available.

   • identified3 Nov, 19:14

     **2026-11-03T02:14:03.275Z** — We are investigating delays in messages presented, while no messages are lost. We expect to provide another update in 1 hour or as soon as more information becomes available **2026-11-03T02:50:08.834Z** — Our engineering team has identified and mitigated the issue causing delays in messages which were presented, while no messages were lost we continue to investigate the root cause. We expect to provide another update in 1 hour or as soon as more information becomes available **2026-11-03T04:53:46.056Z** — Our engineering team has identified and mitigated the issue causing delays in messages which were presented, while no messages were lost we continue to investigate the root cause. We expect to provide another update in 2 hour or as soon as more information becomes available **2026-11-03T06:55:32.255Z** — Our engineering team has identified and mitigated the issue causing delays in messages which were presented, while no messages were lost we continue to investigate the root cause. We expect to provide another update in 4 hour or as soon as more information becomes available. **2026-11-03T10:51:38.882Z** — Our engineering team has identified and mitigated the issue causing delays in messages which were presented, while no messages were lost we continue to investigate the root cause. We expect to provide another update in 8 hours or as soon as more information becomes available. **2026-11-03T19:13:31.030Z** — The message delays were caused by an issue with a single host and affected only a portion of SMS traffic for approximately one hour. Service was restored and has been stable since with no data loss. We have applied a preventive measure to avoid a recurrence and are validating a permanent fix. We will share our next update in 8 hours or as soon as new information is available.

   • identified3 Nov, 10:56

     **2026-11-03T02:14:03.275Z** — We are investigating delays in messages presented, while no messages are lost. We expect to provide another update in 1 hour or as soon as more information becomes available **2026-11-03T02:50:08.834Z** — Our engineering team has identified and mitigated the issue causing delays in messages which were presented, while no messages were lost we continue to investigate the root cause. We expect to provide another update in 1 hour or as soon as more information becomes available **2026-11-03T04:53:46.056Z** — Our engineering team has identified and mitigated the issue causing delays in messages which were presented, while no messages were lost we continue to investigate the root cause. We expect to provide another update in 2 hour or as soon as more information becomes available **2026-11-03T06:55:32.255Z** — Our engineering team has identified and mitigated the issue causing delays in messages which were presented, while no messages were lost we continue to investigate the root cause. We expect to provide another update in 4 hour or as soon as more information becomes available. **2026-11-03T10:51:38.882Z** — Our engineering team has identified and mitigated the issue causing delays in messages which were presented, while no messages were lost we continue to investigate the root cause. We expect to provide another update in 8 hours or as soon as more information becomes available.

   • identified3 Nov, 10:54

     **2026-11-03T02:14:03.275Z** — We are investigating delays in messages presented, while no messages are lost. We expect to provide another update in 1 hour or as soon as more information becomes available **2026-11-03T02:50:08.834Z** — Our engineering team has identified and mitigated the issue causing delays in messages which were presented, while no messages were lost we continue to investigate the root cause. We expect to provide another update in 1 hour or as soon as more information becomes available **2026-11-03T04:53:46.056Z** — Our engineering team has identified and mitigated the issue causing delays in messages which were presented, while no messages were lost we continue to investigate the root cause. We expect to provide another update in 2 hour or as soon as more information becomes available **2026-11-03T06:55:32.255Z** — Our engineering team has identified and mitigated the issue causing delays in messages which were presented, while no messages were lost we continue to investigate the root cause. We expect to provide another update in 4 hour or as soon as more information becomes available.

   • identified3 Nov, 10:52

     **2026-11-03T02:14:03.275Z** — We are investigating delays in messages presented, while no messages are lost. We expect to provide another update in 1 hour or as soon as more information becomes available **2026-11-03T02:50:08.834Z** — Our engineering team has identified and mitigated the issue causing delays in messages which were presented, while no messages were lost we continue to investigate the root cause. We expect to provide another update in 1 hour or as soon as more information becomes available **2026-11-03T04:53:46.056Z** — Our engineering team has identified and mitigated the issue causing delays in messages which were presented, while no messages were lost we continue to investigate the root cause. We expect to provide another update in 2 hour or as soon as more information becomes available **2026-11-03T06:55:32.255Z** — Our engineering team has identified and mitigated the issue causing delays in messages which were presented, while no messages were lost we continue to investigate the root cause. We expect to provide another update in 4 hour or as soon as more information becomes available. **2026-11-03T10:51:38.882Z** — Our engineering team has identified and mitigated the issue causing delays in messages which were presented, while no messages were lost we continue to investigate the root cause. We expect to provide another update in 8 hours or as soon as more information becomes available.

   • identified3 Nov, 06:56

     **2026-11-03T02:14:03.275Z** — We are investigating delays in messages presented, while no messages are lost. We expect to provide another update in 1 hour or as soon as more information becomes available **2026-11-03T02:50:08.834Z** — Our engineering team has identified and mitigated the issue causing delays in messages which were presented, while no messages were lost we continue to investigate the root cause. We expect to provide another update in 1 hour or as soon as more information becomes available **2026-11-03T04:53:46.056Z** — Our engineering team has identified and mitigated the issue causing delays in messages which were presented, while no messages were lost we continue to investigate the root cause. We expect to provide another update in 2 hour or as soon as more information becomes available **2026-11-03T06:55:32.255Z** — Our engineering team has identified and mitigated the issue causing delays in messages which were presented, while no messages were lost we continue to investigate the root cause. We expect to provide another update in 4 hour or as soon as more information becomes available.

   • identified3 Nov, 04:54

     **2026-11-03T02:14:03.275Z** — We are investigating delays in messages presented, while no messages are lost. We expect to provide another update in 1 hour or as soon as more information becomes available **2026-11-03T02:50:08.834Z** — Our engineering team has identified and mitigated the issue causing delays in messages which were presented, while no messages were lost we continue to investigate the root cause. We expect to provide another update in 1 hour or as soon as more information becomes available **2026-11-03T04:53:46.056Z** — Our engineering team has identified and mitigated the issue causing delays in messages which were presented, while no messages were lost we continue to investigate the root cause. We expect to provide another update in 2 hour or as soon as more information becomes available

   • identified3 Nov, 02:50

     **2026-11-03T02:14:03.275Z** — We are investigating delays in messages presented, while no messages are lost. We expect to provide another update in 1 hour or as soon as more information becomes available **2026-11-03T02:50:08.834Z** — Our engineering team has identified and mitigated the issue causing delays in messages which were presented, while no messages were lost we continue to investigate the root cause. We expect to provide another update in 1 hour or as soon as more information becomes available

   • investigating3 Nov, 02:16

     **2026-11-03T02:14:03.275Z** — We are investigating delays in messages presented, while no messages are lost. We expect to provide another update in 1 hour or as soon as more information becomes available

7. Russia SMS Carrier Maintenance - MTT

   Maintenance · 2 Nov 2026, 20:55 · resolved 3 days ago

   • resolved2 Nov, 22:00

     The scheduled maintenance window ended at 2 Nov 2026, 22:00. Closed automatically by the status page.

   • monitoring2 Nov, 20:56

     **2026-11-02T17:48:01.752Z** — <p>The MTT network in Russia is conducting a planned maintenance from 02 November 2026 at 12:55 PST until 02 November 2026 at 14:00 PST. During the maintenance window, there could be intermittent delays delivering SMS to MTT Russia handsets.<br><br>We are aware of the short notice and are working with our Carrier Partners to provide earlier notification where possible.</p> **2026-11-02T19:55:07.586Z** — Maintenance will begin as scheduled in 60 minutes. **2026-11-02T20:55:08.795Z** — Scheduled maintenance is currently in progress. We will provide updates as necessary.

   • identified2 Nov, 19:56

     **2026-11-02T17:48:01.752Z** — <p>The MTT network in Russia is conducting a planned maintenance from 02 November 2026 at 12:55 PST until 02 November 2026 at 14:00 PST. During the maintenance window, there could be intermittent delays delivering SMS to MTT Russia handsets.<br><br>We are aware of the short notice and are working with our Carrier Partners to provide earlier notification where possible.</p> **2026-11-02T19:55:07.586Z** — Maintenance will begin as scheduled in 60 minutes.

   • resolved2 Nov, 17:58

     Auto-resolved by the status page: the vendor stopped reporting this incident in their feed.

   • resolved2 Nov, 17:50

     Auto-resolved by the status page: the vendor stopped reporting this incident in their feed.

   • identified2 Nov, 17:48

     **2026-11-02T17:48:01.752Z** — <p>The MTT network in Russia is conducting a planned maintenance from 02 November 2026 at 12:55 PST until 02 November 2026 at 14:00 PST. During the maintenance window, there could be intermittent delays delivering SMS to MTT Russia handsets.<br><br>We are aware of the short notice and are working with our Carrier Partners to provide earlier notification where possible.</p>

8. Russia SMS Carrier Maintenance - MegaFon

   Maintenance · 2 Nov 2026, 20:00 · resolved 3 days ago

   • resolved3 Nov, 00:00

     The scheduled maintenance window ended at 3 Nov 2026, 00:00. Closed automatically by the status page.

   • monitoring2 Nov, 20:00

     **2026-10-27T23:11:27.138Z** — <p>The MegaFon network in Russia is conducting a planned maintenance from 02 November 2026 at 12:00 PST until 02 November 2026 at 16:00 PST. During the maintenance window, there could be intermittent delays delivering SMS to MegaFon Russia handsets.</p> **2026-11-02T19:01:10.072Z** — Maintenance will begin as scheduled in 60 minutes. **2026-11-02T20:00:07.793Z** — Scheduled maintenance is currently in progress. We will provide updates as necessary.

   • identified2 Nov, 19:02

     **2026-10-27T23:11:27.138Z** — <p>The MegaFon network in Russia is conducting a planned maintenance from 02 November 2026 at 12:00 PST until 02 November 2026 at 16:00 PST. During the maintenance window, there could be intermittent delays delivering SMS to MegaFon Russia handsets.</p> **2026-11-02T19:01:10.072Z** — Maintenance will begin as scheduled in 60 minutes.

   • identified27 Oct, 23:12

     **2026-10-27T23:11:27.138Z** — <p>The MegaFon network in Russia is conducting a planned maintenance from 02 November 2026 at 12:00 PST until 02 November 2026 at 16:00 PST. During the maintenance window, there could be intermittent delays delivering SMS to MegaFon Russia handsets.</p>

9. Some Customers May Have Incorrect Balances Reflected on Their Account

   Minor · 2 Nov 2026, 16:37 · resolved 1 day ago

   • resolved4 Nov, 01:26

     Auto-resolved by the status page: the vendor stopped reporting this incident in their feed.

   • investigating3 Nov, 07:50

     **2026-11-02T16:37:49.837Z** — Our engineering team is actively investigating the issue causing incorrect balances to be reflected on customer accounts. We are working to deploy a fix as quickly as possible. We will provide another update within the next 30 minutes, or sooner if additional information becomes available. **2026-11-02T17:30:01.852Z** — Our engineering team is still actively investigating the issue causing incorrect balances to be reflected on customer accounts. We are working to deploy a fix as quickly as possible. We will provide another update within the next hour, or sooner if additional information becomes available. **2026-11-02T18:36:53.295Z** — Our engineering team is still actively investigating the issue. We will provide another update within the next hour, or sooner if additional information becomes available. **2026-11-02T19:34:42.543Z** — Our engineering team is still actively investigating the issue. We will provide another update within the next hour, or sooner if additional information becomes available. **2026-11-02T23:29:47.961Z** — Our engineering team is still actively investigating the issue. We will provide another update within the next hour, or sooner if additional information becomes available. **2026-11-03T07:27:13.943Z** — Our engineering team is still actively investigating the issue. We will provide another update within the next hour, or sooner if additional information becomes available. **2026-11-03T07:48:27.312Z** — Our engineering team is still actively investigating the issue. The next update will be shared as soon as more information becomes available.

   • investigating3 Nov, 07:28

     **2026-11-02T16:37:49.837Z** — Our engineering team is actively investigating the issue causing incorrect balances to be reflected on customer accounts. We are working to deploy a fix as quickly as possible. We will provide another update within the next 30 minutes, or sooner if additional information becomes available. **2026-11-02T17:30:01.852Z** — Our engineering team is still actively investigating the issue causing incorrect balances to be reflected on customer accounts. We are working to deploy a fix as quickly as possible. We will provide another update within the next hour, or sooner if additional information becomes available. **2026-11-02T18:36:53.295Z** — Our engineering team is still actively investigating the issue. We will provide another update within the next hour, or sooner if additional information becomes available. **2026-11-02T19:34:42.543Z** — Our engineering team is still actively investigating the issue. We will provide another update within the next hour, or sooner if additional information becomes available. **2026-11-02T23:29:47.961Z** — Our engineering team is still actively investigating the issue. We will provide another update within the next hour, or sooner if additional information becomes available. **2026-11-03T07:27:13.943Z** — Our engineering team is still actively investigating the issue. We will provide another update within the next hour, or sooner if additional information becomes available.

   • investigating2 Nov, 23:31

     **2026-11-02T16:37:49.837Z** — Our engineering team is actively investigating the issue causing incorrect balances to be reflected on customer accounts. We are working to deploy a fix as quickly as possible. We will provide another update within the next 30 minutes, or sooner if additional information becomes available. **2026-11-02T17:30:01.852Z** — Our engineering team is still actively investigating the issue causing incorrect balances to be reflected on customer accounts. We are working to deploy a fix as quickly as possible. We will provide another update within the next hour, or sooner if additional information becomes available. **2026-11-02T18:36:53.295Z** — Our engineering team is still actively investigating the issue. We will provide another update within the next hour, or sooner if additional information becomes available. **2026-11-02T19:34:42.543Z** — Our engineering team is still actively investigating the issue. We will provide another update within the next hour, or sooner if additional information becomes available. **2026-11-02T23:29:47.961Z** — Our engineering team is still actively investigating the issue. We will provide another update within the next hour, or sooner if additional information becomes available.

   • investigating2 Nov, 19:36

     **2026-11-02T16:37:49.837Z** — Our engineering team is actively investigating the issue causing incorrect balances to be reflected on customer accounts. We are working to deploy a fix as quickly as possible. We will provide another update within the next 30 minutes, or sooner if additional information becomes available. **2026-11-02T17:30:01.852Z** — Our engineering team is still actively investigating the issue causing incorrect balances to be reflected on customer accounts. We are working to deploy a fix as quickly as possible. We will provide another update within the next hour, or sooner if additional information becomes available. **2026-11-02T18:36:53.295Z** — Our engineering team is still actively investigating the issue. We will provide another update within the next hour, or sooner if additional information becomes available. **2026-11-02T19:34:42.543Z** — Our engineering team is still actively investigating the issue. We will provide another update within the next hour, or sooner if additional information becomes available.

   • investigating2 Nov, 18:38

     **2026-11-02T16:37:49.837Z** — Our engineering team is actively investigating the issue causing incorrect balances to be reflected on customer accounts. We are working to deploy a fix as quickly as possible. We will provide another update within the next 30 minutes, or sooner if additional information becomes available. **2026-11-02T17:30:01.852Z** — Our engineering team is still actively investigating the issue causing incorrect balances to be reflected on customer accounts. We are working to deploy a fix as quickly as possible. We will provide another update within the next hour, or sooner if additional information becomes available. **2026-11-02T18:36:53.295Z** — Our engineering team is still actively investigating the issue. We will provide another update within the next hour, or sooner if additional information becomes available.

   • investigating2 Nov, 17:36

     **2026-11-02T16:37:49.837Z** — Our engineering team is actively investigating the issue causing incorrect balances to be reflected on customer accounts. We are working to deploy a fix as quickly as possible. We will provide another update within the next 30 minutes, or sooner if additional information becomes available. **2026-11-02T17:30:01.852Z** — Our engineering team is still actively investigating the issue causing incorrect balances to be reflected on customer accounts. We are working to deploy a fix as quickly as possible. We will provide another update within the next hour, or sooner if additional information becomes available.

   • investigating2 Nov, 17:34

     **2026-11-02T16:37:49.837Z** — Our engineering team is actively investigating the issue causing incorrect balances to be reflected on customer accounts. We are working to deploy a fix as quickly as possible. We will provide another update within the next 30 minutes, or sooner if additional information becomes available.

   • investigating2 Nov, 17:30

     **2026-11-02T16:37:49.837Z** — Our engineering team is actively investigating the issue causing incorrect balances to be reflected on customer accounts. We are working to deploy a fix as quickly as possible. We will provide another update within the next 30 minutes, or sooner if additional information becomes available. **2026-11-02T17:30:01.852Z** — Our engineering team is still actively investigating the issue causing incorrect balances to be reflected on customer accounts. We are working to deploy a fix as quickly as possible. We will provide another update within the next hour, or sooner if additional information becomes available.

   • investigating2 Nov, 16:38

     **2026-11-02T16:37:49.837Z** — Our engineering team is actively investigating the issue causing incorrect balances to be reflected on customer accounts. We are working to deploy a fix as quickly as possible. We will provide another update within the next 30 minutes, or sooner if additional information becomes available.

10. SMS Delivery Delays and Failures from Twilio Alphanumeric Sender Type to T-Mobile Austria

    Minor · 2 Nov 2026, 15:32 · resolved 3 days ago

    • resolved2 Nov, 20:46

      Auto-resolved by the status page: the vendor stopped reporting this incident in their feed.

    • monitoring2 Nov, 18:44

      **2026-11-02T15:32:04.350Z** — Twilio customers may be experiencing SMS delivery delays and failures from Twilio Alphanumeric Sender IDs to T-Mobile network subscribers in Austria. Our team is actively investigating this issue. We will provide another update in 1 hour or as soon as more information becomes available. **2026-11-02T15:39:53.470Z** — Twilio customers may be experiencing SMS delivery delays and failures from Twilio Alphanumeric Sender Type to T-Mobile network subscribers in Austria. Our team has identified the cause, and is working to resolve the issue. We will provide another update in 1 hour or as soon as more information becomes available. **2026-11-02T16:40:39.315Z** — Twilio customers may be experiencing SMS delivery delays and failures from Twilio Alphanumeric Sender Type to T-Mobile network subscribers in Austria. Our team has identified the cause, and is working to resolve the issue. We will provide another update in 2 hours or as soon as more information becomes available. **2026-11-02T18:42:36.954Z** — We have observed a recovery in SMS delivery from Twilio Alphanumeric Sender Type to T-Mobile network subscribers in Austria and are monitoring service stability. We will provide another update in 2 hours or as soon as more information becomes available.

    • identified2 Nov, 16:42

      **2026-11-02T15:32:04.350Z** — Twilio customers may be experiencing SMS delivery delays and failures from Twilio Alphanumeric Sender IDs to T-Mobile network subscribers in Austria. Our team is actively investigating this issue. We will provide another update in 1 hour or as soon as more information becomes available. **2026-11-02T15:39:53.470Z** — Twilio customers may be experiencing SMS delivery delays and failures from Twilio Alphanumeric Sender Type to T-Mobile network subscribers in Austria. Our team has identified the cause, and is working to resolve the issue. We will provide another update in 1 hour or as soon as more information becomes available. **2026-11-02T16:40:39.315Z** — Twilio customers may be experiencing SMS delivery delays and failures from Twilio Alphanumeric Sender Type to T-Mobile network subscribers in Austria. Our team has identified the cause, and is working to resolve the issue. We will provide another update in 2 hours or as soon as more information becomes available.

    • identified2 Nov, 15:40

      **2026-11-02T15:32:04.350Z** — Twilio customers may be experiencing SMS delivery delays and failures from Twilio Alphanumeric Sender IDs to T-Mobile network subscribers in Austria. Our team is actively investigating this issue. We will provide another update in 1 hour or as soon as more information becomes available. **2026-11-02T15:39:53.470Z** — Twilio customers may be experiencing SMS delivery delays and failures from Twilio Alphanumeric Sender Type to T-Mobile network subscribers in Austria. Our team has identified the cause, and is working to resolve the issue. We will provide another update in 1 hour or as soon as more information becomes available.

    • investigating2 Nov, 15:34

      **2026-11-02T15:32:04.350Z** — Twilio customers may be experiencing SMS delivery delays and failures from Twilio Alphanumeric Sender IDs to T-Mobile network subscribers in Austria. Our team is actively investigating this issue. We will provide another update in 1 hour or as soon as more information becomes available.