Home
/
Status
/
Service
Cross-channel marketing platform for unified customer experiences.
Source
auto
Category
Analytics
Adapter
STATUSPAGE IO
Verified
Pending review
Current state
Operational
Checked 15m ago
556
Components
0
Active incidents
0
Maintenance
16.67%
90d uptime
WhatsApp Messaging Delays and Failures
Jun 12, 4:23 PM
Normalized official status-page data for incidents, maintenance, components, and history.
16.67%
Known uptime
6 known history days
556
Components tracked
0 outage, 0 degraded
50
Incidents indexed
0 active right now
28
Maintenance windows
0 active or scheduled
Components with the most recent status-page events.
Cluster 10
Operational
Cluster 100
Operational
Cluster 101
Operational
Cluster 102
Operational
Cluster 103
Operational
Component changes, incidents, and maintenance windows grouped by day.
operational
degraded
outage
maintenance
unknown
1
operational days
0
degraded days
5
outage days
0
maintenance days
84
unknown days
Latest outages and degradations detected from the official status page.
The issue affecting WhatsApp messaging has been resolved. Customers should no longer experience delays or failures sending WhatsApp messages. We will continue to monitor to ensure service remains stable.
Our engineering team has completed the fix to the web application in both the US and EU regions. All services are currently functioning normally. Email sends, API traffic, webhooks, and journeys functioned normally throughout this incident. The only impact was being unable to log into the web application and slow page loads. If you continue to experience any issues, please reach out to Support.
This incident has been resolved.
This incident has been resolved.
This incident has been resolved.
We have fully caught up with any backlog on C102 and all queries and activity through C102 are functioning normally. If you continue to experience any issues please contact Support.
This incident has been resolved.
SparkPost’s API issue has been resolved, and we’re no longer seeing elevated 5xx errors or increased latency. Incident has resolved.
Service has fully recovered and all traffic has been restored to app.iterable.com in the US region. The incident lasted from 9:50 am to 10:15 am Pacific Time, impacting both web and API access with elevated 502, 503, and 504 errors. EU region was unaffected.
We experienced a period of delayed sends (including proofs) as well as errors in user updates from 7am to 9am ET. The issue has been resolved. Some delayed messages may still be processing and will be sent shortly. If customers received 500 responses to API requests, they should re-try those calls.
Scheduled and completed maintenance windows are separated from incidents.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The maintenance is complete. You can reach out to CSMs for questions about this maintenance.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
Uptimus tracks the official Iterable status page, normalizes upstream events, and separates incidents from scheduled maintenance.
Official source
https://status.iterable.com
Adapter
STATUSPAGE IO
Alert streams
Incidents, component changes, and maintenance windows.
Public SEO page
Indexable status history for users searching outage information.
Regional reports can be layered on top of official provider status when user signals are available.
Showing 1 to 25 of 556 tracked components.
| Component | Status | Type | Last changed |
|---|---|---|---|
Cluster 5 | Operational | Group | Not recorded |
Cluster 6 | Operational | Group | Not recorded |
Cluster 8 | Operational | Group | Not recorded |
Cluster 9 | Operational | Group | Not recorded |
Cluster 10 | Operational | Group | Not recorded |
Cluster 11 | Operational | Group | Not recorded |
Cluster 12 | Operational | Group | Not recorded |
Cluster 13 | Operational | Group | Not recorded |
Cluster 14 | Operational | Group | Not recorded |
Cluster 15 | Operational | Group | Not recorded |
Cluster 16 | Operational | Group | Not recorded |
Cluster 17 | Operational | Group | Not recorded |
Cluster 18 | Operational | Group | Not recorded |
Cluster 19 | Operational | Group | Not recorded |
Cluster 20 | Operational | Group | Not recorded |
Cluster 21 | Operational | Group | Not recorded |
Cluster 22 | Operational | Group | Not recorded |
Cluster 23 | Operational | Group | Not recorded |
Cluster 24 | Operational | Group | Not recorded |
Cluster 25 | Operational | Group | Not recorded |
Cluster 100 | Operational | Group | Not recorded |
Cluster 101 | Operational | Group | Not recorded |
Cluster 102 | Operational | Group | Not recorded |
Cluster 103 | Operational | Group | Not recorded |
Cluster 104 | Operational | Group | Not recorded |
Follow outages, degraded components, and maintenance updates in your Uptimus workspace with email, push, and webhook alerts.
Official provider components
Incident and maintenance separation
Workspace alerts and webhooks
Related status pages based on category, adapter type, and operational history.
Iterable is currently marked as Operational in Uptimus based on the latest official status page check.
Supported status page providers are checked continuously by our scraper scheduler. The public page is cached briefly for SEO and performance.
No. Uptimus stores incidents and maintenance windows separately when the upstream provider exposes enough detail.
Yes. Create an Uptimus workspace, follow this provider, and choose email, push, or webhook notifications.
