Network · data from 2026-11-12
AS37098 Globe Internet
Registry name: globe internet limited - globe internet limited, MW · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS37098, 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.
| 2c0f:f9a0::/36 | No ROA | RIR databaseAFRINIC | 634 100% |
| 41.77.8.0/24 | Valid | RIR databaseAFRINIC | 671 100% |
| 41.77.9.0/24 | Valid | RIR databaseAFRINIC | 671 100% |
| 41.77.10.0/24 | Valid | RIR databaseAFRINIC | 671 100% |
| 41.77.11.0/24 | Valid | RIR databaseAFRINIC | 671 100% |
| 41.77.12.0/24 | Valid | RIR databaseAFRINIC | 671 100% |
| 41.77.14.0/24 | Valid | RIR databaseAFRINIC | 671 100% |
| 41.77.15.0/24 | Valid | RIR databaseAFRINIC | 671 100% |
| 41.216.229.0/24 | Valid | RIR databaseAFRINIC | 671 100% |
| 41.216.230.0/24 | Valid | RIR databaseAFRINIC | 671 100% |
| 41.216.231.0/24 | Valid | RIR databaseAFRINIC | 671 100% |
| 154.66.120.0/24 | Valid | RIR databaseAFRINIC | 671 100% |
| 154.66.121.0/24 | Valid | RIR databaseAFRINIC | 671 100% |
| 154.66.122.0/24 | Valid | RIR databaseAFRINIC | 671 100% |
| 154.66.123.0/24 | Valid | RIR databaseAFRINIC | 671 100% |
| 154.66.124.0/24 | Valid | RIR databaseAFRINIC | 671 100% |
| 154.66.125.0/24 | Valid | RIR databaseAFRINIC | 671 100% |
| 154.66.126.0/24 | Valid | RIR databaseAFRINIC | 671 100% |
| 154.66.127.0/24 | Valid | RIR databaseAFRINIC | 671 100% |
| 41.77.13.0/24 | Valid | RIR databaseAFRINIC | 668 99% |
| 41.216.228.0/24 | Valid | RIR databaseAFRINIC | 668 99% |
AS-SET
PeeringDB's irr_as_set for AS37098: AS-37098. 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 (AS37098 isn't in the set, or no route object for AS37098 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 | AS37098 in it | Not covered |
|---|---|---|---|---|---|
| AS-37098 | AFRINIC | 5 | 1 | 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 18 are in fix.csv.
- ROA: none1
- Route object: not announced17
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2c0f:f9a0::/36 | No ROA covers it. Add a ROA for AS37098, maxLength 36. |
Route objects not announced
Route objects with origin AS37098 whose prefix no peer sees AS37098 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2c0f:f9a0::/32 | AFRINIC | No ROA |
| 2c0f:f9a0:1000::/36 | AFRINIC | No ROA |
| 2c0f:f9a0:1000::/48 | AFRINIC | No ROA |
| 2c0f:f9a0:2000::/36 | AFRINIC | No ROA |
| 2c0f:f9a0:3000::/36 | AFRINIC | No ROA |
| 2c0f:f9a0:4000::/36 | AFRINIC | No ROA |
| 2c0f:f9a0:5000::/36 | AFRINIC | No ROA |
| 2c0f:f9a0:6000::/36 | AFRINIC | No ROA |
| 2c0f:f9a0:7000::/36 | AFRINIC | No ROA |
| 2c0f:f9a0:8000::/36 | AFRINIC | No ROA |
| 2c0f:f9a0:9000::/36 | AFRINIC | No ROA |
| 2c0f:f9a0:a000::/36 | AFRINIC | No ROA |
| 2c0f:f9a0:b000::/36 | AFRINIC | No ROA |
| 2c0f:f9a0:c000::/36 | AFRINIC | No ROA |
| 2c0f:f9a0:d000::/36 | AFRINIC | No ROA |
| 2c0f:f9a0:e000::/36 | AFRINIC | No ROA |
| 2c0f:f9a0:f000::/36 | AFRINIC | No ROA |
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.