Resolved
OpenAI · Incident record · Jun 7, 15:08 UTC

Disruption in service availabilty for Free and Go users

41/100
User-Impact Score · Degraded
2026-06-07 15:12 UTC — UIS 41
startedresolved

2h 58m · OpenAI · scope unspecified · single-source — not confirmed.

Cite this incidentBibTeX · APA · MLA · Chicago · RIS
ai-receipts. (2026, June 7). Disruption in service availabilty for Free and Go users [Incident record, methodology v1.0]. ai-receipts. https://aireceipts.org/incidents/openai:01KTHA1XMAS77H4GMQBKSNPK71
Embed this incidentiframe · CC-BY-4.0
<iframe src="https://aireceipts.org/incidents/openai:01KTHA1XMAS77H4GMQBKSNPK71?embed=1" title="OpenAI: Disruption in service availabilty for Free and Go users — ai-receipts incident record" width="100%" height="420" loading="lazy" style="border:1px solid #e4e4e7"></iframe>
<p><a href="https://aireceipts.org/incidents/openai:01KTHA1XMAS77H4GMQBKSNPK71">Source: ai-receipts</a> · CC-BY-4.0</p>

Data record

UIS
41/100
Status
resolved
Started (UTC)
2026-06-07 15:08
Duration
2h 58m
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 1,310 provider updates and 6 of 6 matched signal observations. Full record in /data (1,210 additional rows).

  1. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  2. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  3. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  4. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  5. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  6. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  7. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  8. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  9. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  10. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  11. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  12. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  13. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  14. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  15. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  16. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  17. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  18. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  19. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  20. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  21. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  22. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  23. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  24. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  25. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  26. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  27. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  28. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  29. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  30. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  31. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  32. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  33. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  34. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  35. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  36. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  37. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  38. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  39. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  40. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  41. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  42. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  43. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  44. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  45. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  46. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  47. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  48. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  49. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  50. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  51. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  52. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  53. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  54. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  55. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  56. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  57. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  58. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  59. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  60. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  61. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  62. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  63. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  64. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  65. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  66. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  67. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  68. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  69. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  70. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  71. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  72. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  73. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  74. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  75. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  76. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  77. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  78. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  79. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  80. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  81. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  82. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  83. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  84. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  85. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  86. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  87. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  88. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  89. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  90. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  91. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  92. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  93. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  94. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  95. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  96. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  97. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  98. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  99. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  100. Jun 7, 15:08 UTC
    [identified]

    We have identified the issue for the listed services. We are currently working on a mitigation.

    permalink
  101. Jun 7, 15:08 UTC
    First independent confirmation
  102. Jun 7, 17:02 UTC
    [hn keyword]

    Proliferate (YC S25) is hiring to building open source Codex

    permalink
  103. Jun 7, 17:02 UTC
    First official acknowledgment
    114 min after ai-receipts confirmation
  104. Jun 7, 17:07 UTC
    [hn keyword]

    Proliferate (YC S25) is hiring to building open source Codex

    permalink
  105. Jun 7, 17:12 UTC
    [hn keyword]

    Proliferate (YC S25) is hiring to building open source Codex

    permalink
  106. Jun 7, 17:17 UTC
    [hn keyword]

    Proliferate (YC S25) is hiring to building open source Codex

    permalink
  107. Jun 7, 17:22 UTC
    [hn keyword]

    Proliferate (YC S25) is hiring to building open source Codex

    permalink
  108. Jun 7, 17:27 UTC
    [hn keyword]

    Proliferate (YC S25) is hiring to building open source Codex

    permalink