Network · data from 2026-11-12
AS34624 Megaspace Internet Services
Registry name: MEGASPACE-AS Megaspace Internet Services GmbH, DE · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS34624, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
| 89.35.2.0/24 | Valid | Nonecovered by 89.35.2.0/23 | 673 100% |
| 89.191.72.0/24 | Valid | Nonecovered by 89.191.64.0/19 | 673 100% |
| 46.253.16.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 89.35.2.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 93.115.33.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.238.60.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 89.191.64.0/19 | Valid | RIR databaseRIPE | 670 100% |
| 2a00:1930::/32 | Valid | RIR databaseRIPE | 633 100% |
AS-SET
PeeringDB's irr_as_set for AS34624: RIPE::AS-MEGASPACE. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS34624 isn't in the set, or no route object for AS34624 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS34624 in it | Not covered |
|---|---|---|---|---|---|
| RIPE::AS-MEGASPACE | RIPE | 2 | 2 | Yes | 0 |
Fix list
The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 7 are in fix.csv.
- Route object: none2
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 89.35.2.0/24 | No route object for it. A route object for 89.35.2.0/23 with origin AS34624 covers it (filters allowing more-specifics accept it). Add a route object with origin AS34624 in the RIR database for the space. |
| Route object: none | 89.191.72.0/24 | No route object for it. A route object for 89.191.64.0/19 with origin AS34624 covers it (filters allowing more-specifics accept it). Add a route object with origin AS34624 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS34624 whose prefix no peer sees AS34624 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 31.170.200.0/21 | RIPE | Valid |
| 31.170.208.0/20 | RIPE | Valid |
| 86.107.191.0/24 | RIPE | Valid |
| 89.40.134.0/23 | RIPE | Valid |
| 185.71.124.0/22 | RIPE | Valid |
Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.