Back to overview
Downtime

图片存储中断

May 23 at 10:14pm HKT
Affected services
Picture storage

Resolved
May 23 at 11:17pm HKT

已恢复

Created
May 23 at 10:14pm HKT

Incident summary for Picture storage (May 23 at 01:49pm BST)
Cause: Status 403
Started at: May 23 at 01:49pm BST
Length: 3 minutes
View incident in Better Stack ↗

AI post-mortem
The storage endpoint started returning 403 Forbidden errors from multiple regions, triggering the monitor alert. Within a few minutes it began serving requests normally again, and the incident auto-resolved after the brief cooldown.

Metadata

Request duration: 0.672338

Response code: 403

Timeline

Received a status 403 error at img.opui.me/ when checked from 91.107.221.68. 🇪🇺 Europe · May 23, 2025 at 1:49pm BST
Page response · May 23, 2025 at 1:49pm BST

403 Forbidden

403 Forbidden
nginx

Received a status 403 error at img.opui.me/ when checked from 139.162.121.226. 🇯🇵 Asia · May 23, 2025 at 1:49pm BST
Page response · May 23, 2025 at 1:49pm BST

403 Forbidden

403 Forbidden
nginx

Received a status 403 error at img.opui.me/ when checked from 194.195.253.108. 🇦🇺 Australia · May 23, 2025 at 1:49pm BST
Page response · May 23, 2025 at 1:49pm BST

403 Forbidden

403 Forbidden
nginx

Waiting for 1 minute before starting the incident. · May 23, 2025 at 1:49pm BST
Page response · May 23, 2025 at 1:49pm BST

403 Forbidden

403 Forbidden
nginx

Incident started. · May 23, 2025 at 1:50pm BST
Sent an email to mian hai at . · May 23, 2025 at 1:50pm BST
Monitor recovered. 🇦🇺 Australia · May 23, 2025 at 1:52pm BST
Monitor recovered. 🇯🇵 Asia · May 23, 2025 at 1:52pm BST
Monitor recovered. 🇪🇺 Europe · May 23, 2025 at 1:52pm BST
Waiting for 3 minutes before auto-resolving the incident, and postponing all escalations. · May 23, 2025 at 1:52pm BST
Incident resolved automatically. · May 23, 2025 at 1:55pm BST