Twilio: Change in How Super SIM Data Usage is Reported for Some Queries to the UsageRecords API
Timeline of updates
- resolved
We have determined that we will not be able to revert the unannounced change in API behavior without the underlying usage reporting services becoming degraded, resulting in other queries also failing. We have sent out a detailed email to recent users of the Super SIM UsageRecords API with additional details. We will be updating the UsageRecords API documentation to reflect the new behavior. We suggest you consider changing all queries to this API for periods greater than 24 hours to use timestamps that fall on UTC hour boundaries to ensure you get accurate and consistent results for your requested start and end times. You may need to rerun reports or adjust amounts persisted to your own systems if you recorded excessive data usage due this unannounced change in API behavior. We apologize for any inconvenience that this causes you
From Twilio’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.twilio.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Twilio, started 2024-04-25 19:07 UTC, resolved after 5 d, 1 update(s).
- Title
- Change in How Super SIM Data Usage is Reported for Some Queries to the UsageRecords API
- Vendor
- Twilio
- Date
- URL
- https://rewindex.com/company/twilio/incidents/jxrxgtvmzqk2
Twilio profileRecent Twilio incidentsAll outages on April 25, 2024Twilio in April 2024MarkdownJSON