Resolved
Cloudflare Workers AI · Incident record · May 28, 01:52 UTC

Elevated number of 5xx errors in Dallas Texas

8/100
User-Impact Score · Informational
startedresolved

-53m · Cloudflare Workers AI · scope unspecified · single-source — not confirmed.

Cite this incidentBibTeX · APA · MLA · Chicago · RIS
ai-receipts. (2026, May 28). Elevated number of 5xx errors in Dallas Texas [Incident record, methodology v1.0]. ai-receipts. https://aireceipts.org/incidents/cloudflare_ai:c6jrdd657mwn
Embed this incidentiframe · CC-BY-4.0
<iframe src="https://aireceipts.org/incidents/cloudflare_ai:c6jrdd657mwn?embed=1" title="Cloudflare Workers AI: Elevated number of 5xx errors in Dallas Texas — ai-receipts incident record" width="100%" height="420" loading="lazy" style="border:1px solid #e4e4e7"></iframe>
<p><a href="https://aireceipts.org/incidents/cloudflare_ai:c6jrdd657mwn">Source: ai-receipts</a> · CC-BY-4.0</p>

Data record

UIS
8/100
Status
resolved
Started (UTC)
2026-05-28 01:52
Duration
-53m
Components
—
Scope
scope unspecified — see methodology limitations
Confirmation
Unconfirmed — single source or weak corroboration only.
Methodology
v1 · how this score was computed · provider status page

Evidence chain

Showing the first 100 of 3,699 provider updates. Full record in /data (3,599 additional rows).

  1. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  2. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  3. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  4. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  5. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  6. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  7. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  8. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  9. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  10. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  11. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  12. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  13. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  14. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  15. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  16. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  17. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  18. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  19. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  20. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  21. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  22. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  23. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  24. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  25. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  26. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  27. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  28. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  29. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  30. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  31. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  32. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  33. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  34. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  35. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  36. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  37. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  38. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  39. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  40. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  41. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  42. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  43. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  44. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  45. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  46. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  47. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  48. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  49. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  50. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  51. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  52. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  53. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  54. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  55. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  56. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  57. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  58. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  59. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  60. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  61. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  62. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  63. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  64. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  65. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  66. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  67. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  68. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  69. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  70. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  71. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  72. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  73. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  74. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  75. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  76. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  77. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  78. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  79. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  80. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  81. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  82. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  83. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  84. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  85. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  86. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  87. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  88. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  89. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  90. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  91. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  92. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  93. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  94. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  95. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  96. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  97. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  98. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  99. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink
  100. May 28, 01:00 UTC
    [resolved]

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

    permalink