bluesky.app live incident monitor
User reports currently show no active issues for bluesky.app
bluesky.app appears to be down or unreachable from our checker.
Current service context
No broad disruption pattern detected at this moment; monitor remains active for fresh signals.
- Cross-check with the official status page for confirmed incident updates.
- Compare with related services to spot wider infrastructure impact.
- Watch the 24h graph for fresh spikes before drawing conclusions.
Report an Issue
Help improve signal quality by sharing your current experience.
bluesky.app incident activity (24h)
Reports down: 0 | Reports recovered: 0 | Unique networks: 0 | Signal score: 8 | External sources (30d): 4
01h
05h
09h
13h
17h
21h
00h
Filled area = total pressure, blue line = internet signal pressure, dashed line = smoothed trend. Only light smoothing is applied to keep spikes visible.
Signal Evidence (24h)
| User reports (down) | 0 |
|---|---|
| User reports (recovered) | 0 |
| Unique networks | 0 |
| Unique countries | 0 |
| External signal score | 8 |
| External sources (30d) | 4 |
Read more about scoring and confidence on the methodology page.
Latest External Sources
| Time (UTC) | Source | Headline | Score |
|---|---|---|---|
| 2026-04-23T18:56:26Z | auto-hnrss-bluesky-app | I built a fitness app in 7 days with no eng background, using Claude as CTO | 2 |
| 2026-04-23T06:37:30Z | auto-google-news-inc-bluesky-app | Bluesky blames DDoS attack for server outages - MSN | 4 |
| 2026-04-23T05:51:16Z | auto-google-news-inc-bluesky-app | Mastodon Hit by DDoS Attack Days After Bluesky Disruption - CXO Digitalpulse | 2 |
| 2026-04-21T17:08:40Z | auto-reddit-search-bluesky-app | My reply that was removed from FRAF regarding the Gio Accusations | 2 |
| 2026-04-21T15:23:19Z | auto-reddit-search-bluesky-app | April 20, 2026 | 2 |
Technical Status
| Domain | bluesky.app |
|---|---|
| HTTP code | - |
| Response time | 54 ms |
| Last check | 2026-04-23T22:05:45Z |
| Redirect | - |
| Error | Get "https://bluesky.app": tls: failed to verify certificate: x509: certificate has expired or is not yet valid: current time 2026-04-23T22:05:45Z is after 2026-04-15T14:40:52Z |
| Resolved IP | 13.48.210.159 |
Latest Checks
| Time | Status | HTTP | Response | Error |
|---|---|---|---|---|
| 2026-04-23T22:05:45Z | down | - | 54 ms | Get "https://bluesky.app": tls: failed to verify certificate: x509: certificate has expired or is not yet valid: current time 2026-04-23T22:05:45Z is after 2026-04-15T14:40:52Z |
| 2026-04-23T21:45:45Z | down | - | 53 ms | Get "https://bluesky.app": tls: failed to verify certificate: x509: certificate has expired or is not yet valid: current time 2026-04-23T21:45:45Z is after 2026-04-15T14:40:52Z |
| 2026-04-23T21:25:48Z | down | - | 56 ms | Get "https://bluesky.app": tls: failed to verify certificate: x509: certificate has expired or is not yet valid: current time 2026-04-23T21:25:48Z is after 2026-04-15T14:40:52Z |
| 2026-04-23T21:06:41Z | down | - | 55 ms | Get "https://bluesky.app": tls: failed to verify certificate: x509: certificate has expired or is not yet valid: current time 2026-04-23T21:06:41Z is after 2026-04-15T14:40:52Z |
| 2026-04-23T20:51:31Z | down | - | 55 ms | Get "https://bluesky.app": tls: failed to verify certificate: x509: certificate has expired or is not yet valid: current time 2026-04-23T20:51:31Z is after 2026-04-15T14:40:52Z |
| 2026-04-23T20:32:52Z | down | - | 27 ms | Get "http://bluesky.app": dial tcp 13.48.210.159:80: connect: connection refused |
Related Services
Compare signals with similar providers and platforms.