Historical
Cloudflare Workers AI · Incident record · May 10, 17:54 UTC

Network Performance Issues in Auckland

Historical record · source provider_api · confidence high
8/100
User-Impact Score · Informational
2026-05-10 17:54 UTC — UIS 82026-05-10 17:54 UTC — UIS 8
startedresolved

0m · Cloudflare Workers AI · scope unspecified · historical record (live confirmation cannot be fabricated retroactively).

Cite this incidentBibTeX · APA · MLA · Chicago · RIS
ai-receipts. (2026, May 10). Network Performance Issues in Auckland [Incident record, methodology v1.0]. ai-receipts. https://aireceipts.org/incidents/cloudflare_ai:qbj7t1t3pdxn
Embed this incidentiframe · CC-BY-4.0
<iframe src="https://aireceipts.org/incidents/cloudflare_ai:qbj7t1t3pdxn?embed=1" title="Cloudflare Workers AI: Network Performance Issues in Auckland — 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:qbj7t1t3pdxn">Source: ai-receipts</a> · CC-BY-4.0</p>

Data record

UIS
8/100
Status
resolved
Started (UTC)
2026-05-10 17:54
Duration
0m
Components
—
Scope
scope unspecified — see methodology limitations
Confirmation
Historical record. Live multi-source confirmation cannot be fabricated retroactively.
Methodology
v1 · how this score was computed · provider status page

Evidence chain

Showing the first 100 of 1,395 provider updates. Full record in /data (1,295 additional rows).

  1. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  2. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  3. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  4. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  5. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  6. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  7. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  8. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  9. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  10. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  11. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  12. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  13. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  14. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  15. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  16. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  17. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  18. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  19. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  20. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  21. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  22. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  23. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  24. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  25. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  26. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  27. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  28. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  29. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  30. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  31. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  32. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  33. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  34. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  35. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  36. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  37. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  38. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  39. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  40. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  41. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  42. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  43. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  44. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  45. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  46. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  47. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  48. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  49. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  50. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  51. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  52. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  53. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  54. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  55. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  56. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  57. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  58. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  59. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  60. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  61. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  62. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  63. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  64. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  65. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  66. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  67. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  68. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  69. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  70. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  71. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  72. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  73. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  74. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  75. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  76. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  77. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  78. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  79. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  80. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  81. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  82. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  83. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  84. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  85. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  86. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  87. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  88. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  89. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  90. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  91. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  92. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  93. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  94. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  95. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  96. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  97. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  98. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  99. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink
  100. May 10, 17:54 UTC
    [resolved]

    Cloudflare identified issues with network performance that occurred for our Auckland, NZ facility between 12:30 and 16:00 UTC today, 2026-05-10. Customers may have noticed increased latency for traffic handled by this facility during this period.

    permalink