Issue with Bandwidth Consumption Reporting

What to do

• Check whether your product depends on Prismic. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 4d it lasted.

  Anything that failed between 2025-06-02 11:42 UTC and 2025-06-06 12:39 UTC may need a replay.

• Subscribe to Prismic's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=prismic works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Prismic 3

1. investigatingJun 2, 2025, 11:42 AM UTC

   We are currently investigating an issue causing inaccurate bandwidth reporting since May 27th. Our team is actively working to identify the root cause and restore correct data. We will provide updates as soon as more information becomes available. Thank you for your patience.

   provider

2. identifiedJun 2, 2025, 2:10 PM UTC

   We have identified the root cause of the issue leading to inaccurate bandwidth consumption reporting. We are currently working with our provider to resolve it. 🔹 **Issue:** Inaccurate reporting of bandwidth consumption

   provider

3. resolvedJun 6, 2025, 12:39 PM UTC

   The issue affecting bandwidth consumption has been fully resolved. All systems are now operational. We apologize for any inconvenience caused and appreciate your patience during this time. If you experience any further issues, please contact [Support Contact]. 🚀 **Thank you for your support!**

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.