Network · data from 2026-11-12
AS61003 GLOBALTELEHOST GlobalTeleHost Corp.
Registry name: GLOBALTELEHOST GlobalTeleHost Corp., CA · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS61003, 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.
| 23.168.88.0/24 | Invalid: origin | Other origin only | 76 11% |
| 216.152.146.0/24 | Valid | RIR databaseARIN | 673 100% |
AS-SET
AS61003 isn't in PeeringDB, where networks name their AS-SET.
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 6 are in fix.csv.
- ROA: origin1
- Route object: none1
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 23.168.88.0/24 | ROAs covering it name AS63023, not AS61003. If AS61003 should announce it, add a ROA for AS61003. |
| Route object: none | 23.168.88.0/24 | Route objects for it name AS63023. Add a route object with origin AS61003 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS61003 whose prefix no peer sees AS61003 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.61.161.0/24 | ARIN | Invalid: origin |
| 149.7.16.0/24 | RADB | No ROA |
| 204.10.194.0/24 | ARIN | Valid |
| 212.193.3.0/24 | 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.