mega.nz live incident monitor
User reports currently show no active issues for mega.nz
mega.nz appears to be up.
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.
mega.nz incident activity (24h)
Reports down: 0 | Reports recovered: 0 | Unique networks: 0 | Signal score: 0 | Monitored source channels: 3
13h
17h
21h
01h
05h
09h
12h
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 | 0 |
| Monitored source channels | 3 |
Read more about scoring and confidence on the methodology page.
Latest External Incident Sources
| Time (UTC) | Source | Headline | Score |
|---|---|---|---|
| 2026-04-26T15:01:53Z | auto-google-news-inc-mega-nz | 20-Day Mega Block at Gaya Junction to Disrupt Train Services, Routes Diverted and Platforms Changed - patnapress.com | 2 |
| 2026-04-25T08:01:32Z | auto-google-news-inc-mega-nz | Is There Sunday Mega Block on April 26, 2026? Will Mumbai Local Train Services Be Affected on Central, - LatestLY | 2 |
| 2026-04-25T04:08:36Z | auto-google-news-inc-mega-nz | India News | ⚡Night Blocks, Mega Block To Disrupt Western & Harbour Line Services This Weekend - LatestLY | 2 |
| 2026-04-24T07:04:28Z | auto-google-news-usage-mega-nz | MegaETH TGE is Set: What to Know - Cryptonews.net | 2 |
| 2026-04-24T05:44:32Z | auto-google-news-usage-mega-nz | MegaETH Token Launch Date Set For April 30 TGE: MEGA Hits 10 Live Apps - Coin Gabbar | 2 |
Technical Status
| Domain | mega.nz |
|---|---|
| HTTP code | 200 |
| Response time | 18 ms |
| Last check | 2026-05-10T10:29:36Z |
| Redirect | - |
| Error | - |
| Resolved IP | 31.216.145.5 |
Latest Checks
| Time | Status | HTTP | Response | Error |
|---|---|---|---|---|
| 2026-05-10T10:29:36Z | up | 200 | 18 ms | - |
| 2026-05-10T09:59:38Z | up | 200 | 17 ms | - |
| 2026-05-10T09:29:40Z | up | 200 | 17 ms | - |
| 2026-05-10T08:59:44Z | up | 200 | 17 ms | - |
| 2026-05-10T08:29:43Z | up | 200 | 17 ms | - |
| 2026-05-10T07:59:48Z | up | 200 | 22 ms | - |
| 2026-05-10T07:34:39Z | up | 200 | 17 ms | - |
| 2026-05-10T07:04:40Z | up | 200 | 26 ms | - |
| 2026-05-10T06:34:39Z | up | 200 | 17 ms | - |
| 2026-05-10T06:04:41Z | up | 200 | 17 ms | - |
| 2026-05-10T05:34:48Z | up | 200 | 17 ms | - |
| 2026-05-10T05:09:36Z | up | 200 | 60 ms | - |
| 2026-05-10T04:34:50Z | up | 200 | 17 ms | - |
| 2026-05-10T04:09:37Z | up | 200 | 17 ms | - |
| 2026-05-10T03:39:36Z | up | 200 | 18 ms | - |
| 2026-05-10T03:09:43Z | up | 200 | 17 ms | - |
| 2026-05-10T02:39:50Z | up | 200 | 17 ms | - |
| 2026-05-10T02:14:37Z | up | 200 | 16 ms | - |
| 2026-05-10T01:44:36Z | up | 200 | 17 ms | - |
| 2026-05-10T01:14:41Z | up | 200 | 16 ms | - |
Related Services
Compare signals with similar providers and platforms.