DownForAI

BlinqIO Incident History

16 major incidents detected for BlinqIO. View live status dashboard →

MajorUnresolved — service still offline

BlinqIO

On 2026-08-14 at 03:16 UTC, DownForAI monitoring detected a significant service issue affecting BlinqIO. The incident is currently being investigated. This incident was detected by our automated probe infrastructure, which checks each monitored surface on a rotating schedule.

Started: Aug 14, 2026, 03:16 UTCStill offline after 63h 21mView service →
MajorResolved

BlinqIO

On 2026-08-10 at 03:30 UTC, DownForAI monitoring detected a significant service issue affecting BlinqIO. The incident has been resolved after approximately 95h 31m. This incident was detected by our automated probe infrastructure, which checks each monitored surface on a rotating schedule.

Started: Aug 10, 2026, 03:30 UTCResolved: Aug 14, 2026, 03:01 UTCDuration: 95h 31mView service →
MajorResolved

BlinqIO

On 2026-08-07 at 03:45 UTC, DownForAI monitoring detected a significant service issue affecting BlinqIO. The incident has been resolved after approximately 71h 16m. This incident was detected by our automated probe infrastructure, which checks each monitored surface on a rotating schedule.

Started: Aug 7, 2026, 03:45 UTCResolved: Aug 10, 2026, 03:01 UTCDuration: 71h 16mView service →
MajorResolved

BlinqIO

On 2026-08-04 at 03:15 UTC, DownForAI monitoring detected a significant service issue affecting BlinqIO. The incident has been resolved after approximately 71h 46m. This incident was detected by our automated probe infrastructure, which checks each monitored surface on a rotating schedule.

Started: Aug 4, 2026, 03:15 UTCResolved: Aug 7, 2026, 03:01 UTCDuration: 71h 46mView service →
MajorResolved

BlinqIO

On 2026-08-01 at 03:45 UTC, DownForAI monitoring detected a significant service issue affecting BlinqIO. The incident has been resolved after approximately 71h 16m. This incident was detected by our automated probe infrastructure, which checks each monitored surface on a rotating schedule.

Started: Aug 1, 2026, 03:45 UTCResolved: Aug 4, 2026, 03:01 UTCDuration: 71h 16mView service →
MajorResolved

BlinqIO

On 2026-07-29 at 04:01 UTC, DownForAI monitoring detected a significant service issue affecting BlinqIO. The incident has been resolved after approximately 71h 0m. This incident was detected by our automated probe infrastructure, which checks each monitored surface on a rotating schedule.

Started: Jul 29, 2026, 04:01 UTCResolved: Aug 1, 2026, 03:01 UTCDuration: 71hView service →
MajorResolved

BlinqIO

On 2026-07-26 at 03:01 UTC, DownForAI monitoring detected a significant service issue affecting BlinqIO. The incident has been resolved after approximately 71h 59m. This incident was detected by our automated probe infrastructure, which checks each monitored surface on a rotating schedule.

Started: Jul 26, 2026, 03:01 UTCResolved: Jul 29, 2026, 03:00 UTCDuration: 71h 59mView service →
MajorResolved

BlinqIO

On 2026-07-23 at 03:45 UTC, DownForAI monitoring detected a significant service issue affecting BlinqIO. The incident has been resolved after approximately 71h 16m. This incident was detected by our automated probe infrastructure, which checks each monitored surface on a rotating schedule.

Started: Jul 23, 2026, 03:45 UTCResolved: Jul 26, 2026, 03:01 UTCDuration: 71h 16mView service →
MajorResolved

BlinqIO

On 2026-07-20 at 03:30 UTC, DownForAI monitoring detected a significant service issue affecting BlinqIO. The incident has been resolved after approximately 71h 31m. This incident was detected by our automated probe infrastructure, which checks each monitored surface on a rotating schedule.

Started: Jul 20, 2026, 03:30 UTCResolved: Jul 23, 2026, 03:01 UTCDuration: 71h 31mView service →
MajorResolved

BlinqIO

On 2026-07-17 at 03:15 UTC, DownForAI monitoring detected a significant service issue affecting BlinqIO. The incident has been resolved after approximately 71h 45m. This incident was detected by our automated probe infrastructure, which checks each monitored surface on a rotating schedule.

Started: Jul 17, 2026, 03:15 UTCResolved: Jul 20, 2026, 03:00 UTCDuration: 71h 45mView service →
MajorResolved

BlinqIO

On 2026-07-15 at 03:00 UTC, DownForAI monitoring detected a significant service issue affecting BlinqIO. The incident has been resolved after approximately 48h 1m. This incident was detected by our automated probe infrastructure, which checks each monitored surface on a rotating schedule.

Started: Jul 15, 2026, 03:00 UTCResolved: Jul 17, 2026, 03:01 UTCDuration: 48h 1mView service →
MajorResolved

BlinqIO

On 2026-07-12 at 03:01 UTC, DownForAI monitoring detected a significant service issue affecting BlinqIO. The incident has been resolved after approximately 71h 59m. This incident was detected by our automated probe infrastructure, which checks each monitored surface on a rotating schedule.

Started: Jul 12, 2026, 03:01 UTCResolved: Jul 15, 2026, 03:00 UTCDuration: 71h 59mView service →
MajorResolved

BlinqIO

On 2026-07-09 at 03:45 UTC, DownForAI monitoring detected a significant service issue affecting BlinqIO. The incident has been resolved after approximately 71h 15m. This incident was detected by our automated probe infrastructure, which checks each monitored surface on a rotating schedule.

Started: Jul 9, 2026, 03:45 UTCResolved: Jul 12, 2026, 03:00 UTCDuration: 71h 15mView service →
MajorResolved

BlinqIO

On 2026-07-06 at 03:30 UTC, DownForAI monitoring detected a significant service issue affecting BlinqIO. The incident has been resolved after approximately 71h 30m. This incident was detected by our automated probe infrastructure, which checks each monitored surface on a rotating schedule.

Started: Jul 6, 2026, 03:30 UTCResolved: Jul 9, 2026, 03:00 UTCDuration: 71h 30mView service →
MajorResolved

BlinqIO

On 2026-07-03 at 04:15 UTC, DownForAI monitoring detected a significant service issue affecting BlinqIO. The incident has been resolved after approximately 70h 45m. This incident was detected by our automated probe infrastructure, which checks each monitored surface on a rotating schedule.

Started: Jul 3, 2026, 04:15 UTCResolved: Jul 6, 2026, 03:00 UTCDuration: 70h 45mView service →
MajorResolved

BlinqIO

On 2026-06-30 at 10:00 UTC, DownForAI monitoring detected a significant service issue affecting BlinqIO. The incident has been resolved after approximately 65h 0m. This incident was detected by our automated probe infrastructure, which checks each monitored surface on a rotating schedule.

Started: Jun 30, 2026, 10:00 UTCResolved: Jul 3, 2026, 03:00 UTCDuration: 65hView service →
← Back to all incidents