Aloware Outage History

Aloware is up right now

Pingoru has recorded 20 incidents for Aloware: 0 in the last 12 months and 0 in the last 90 days.

Source: status.aloware.com

20incidents recorded
0last 12 months
0last 90 days
–typical duration
Incidents per month
012AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Aloware in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202600 of 720 (0%)
May 202600 of 744 (0%)
June 202600 of 720 (0%)
July 202600 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 526 (0%)

Incidents, newest first

Minor October 20, 2025 Calls and Messages are intermittently failing 7h 25m Inbound calls, Messaging (SMS) - Apps, Outbound calls, Messaging (SMS) - Sequences and 2 more

Started Oct 20, 2025, 03:11 PM UTC· resolved Oct 20, 2025, 10:36 PM UTC

  1. monitoring Oct 20, 2025, 03:11 PM UTC

    We’re currently experiencing intermittent issues affecting messaging and calling services due to an ongoing outage impacting Twilio, our underlying communications provider. Twilio has reported that the disruption stems from a major AWS outage (https://health.aws.amazon.com/health/status) in the US-East-1 region. Our team is closely monitoring the situation and working directly with Twilio to minimize the impact on our users. Some calls, texts may experience temporary delays or interruptions. We’ll continue to post updates as the situation evolves. Thank you for your patience and understanding.

  2. monitoring Oct 20, 2025, 04:13 PM UTC

    We’re continuing to monitor an ongoing issue affecting some calling and messaging services. We will provide another update in 60 minutes or as soon as more information becomes available.

  3. monitoring Oct 20, 2025, 07:14 PM UTC

    We’re continuing to monitor an ongoing issue affecting some calling and messaging services. We will provide another update in 60 minutes or as soon as more information becomes available.

  4. monitoring Oct 20, 2025, 07:15 PM UTC

    We’re continuing to monitor an ongoing issue affecting some calling and messaging services. We will provide another update in 60 minutes or as soon as more information becomes available.

  5. monitoring Oct 20, 2025, 07:15 PM UTC

    We’re continuing to monitor an ongoing issue affecting some calling and messaging services. We will provide another update in 60 minutes or as soon as more information becomes available.

  6. monitoring Oct 20, 2025, 08:13 PM UTC

    We’re continuing to monitor an ongoing issue affecting some calling and messaging services. Service performance is improving, but intermittent issues may still occur. We will provide another update in 60 minutes or as soon as more information becomes available.

  7. monitoring Oct 20, 2025, 09:16 PM UTC

    We’re continuing to monitor an ongoing issue affecting some calling and messaging services. Service performance is improving, but intermittent issues may still occur. We will provide another update in 60 minutes or as soon as more information becomes available.

  8. monitoring Oct 20, 2025, 10:09 PM UTC

    The underlying AWS incident appears to be resolved, but we are continuing to monitor system performance to ensure full recovery.

  9. resolved Oct 20, 2025, 10:36 PM UTC

    This incident appears to be resolved, and all services are now working as expected.

Read the full incident report →

Minor March 19, 2025 Reporting delays and failure 2h 38m Admin Dashboard, Reporting

Started Mar 19, 2025, 02:38 PM UTC· resolved Mar 19, 2025, 05:16 PM UTC

  1. investigating Mar 19, 2025, 02:38 PM UTC

    We have identified an issue causing a delay in the reporting data and are actively working to resolve it. During this time, some reports, graphs, and tables might not show accurate data. This includes Classic's dashboard, reports, and certain other statistics within Talk. Rest assured, no data has been lost—this is simply a delay. Our team is clearing the backlog, and once resolved, all data will be fully viewable. We will continue to provide periodic updates on this incident until the issue is fully cleared. Thank you for your patience and understanding

  2. resolved Mar 19, 2025, 05:16 PM UTC

    We have recovered our reporting system and all dashboards and graphs are running smoothly. While the underlying issues with AWS continue to persist, we believe our secondary mechanism is robust enough till AWS fixes the root cause. No data has been lost and today's call and text performance is showing on all reports.

Read the full incident report →

Minor February 7, 2025 Reporting Data Delay 1h 14m Reporting

Started Feb 07, 2025, 01:56 AM UTC· resolved Feb 07, 2025, 03:11 AM UTC

  1. identified Feb 07, 2025, 01:56 AM UTC

    We have identified an issue causing a delay in the reporting data and are actively working to resolve it. During this time, some reports, graphs, and tables might not show accurate data. Please rest assured, no data has been lost—this is simply a delay. Our team is clearing the backlog, and once resolved, all data will be fully viewable. We will continue to provide periodic updates on this incident until the issue is fully cleared. Thank you for your patience and understanding

  2. resolved Feb 07, 2025, 03:11 AM UTC

    This incident has been resolved. All data should be fully back in sync. We will continue to monitor the situation closely for any recurrence.

Read the full incident report →