Network · data from 2026-11-12
AS32768 MOBIUS-COMMUNICATIONS-NE - HEMINGFORD TELEPHONE
Registry name: MOBIUS-COMMUNICATIONS-NE - HEMINGFORD TELEPHONE, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS32768, 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.
| 147.160.144.0/24 | No ROA | Other origin only | 672 100% |
| 23.29.80.0/20 | Valid | RIR databaseARIN | 671 100% |
AS-SET
AS32768 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 59 are in fix.csv.
- ROA: none1
- Route object: none1
- Route object: not announced57
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 147.160.144.0/24 | No ROA covers it. Add a ROA for AS32768, maxLength 24. |
| Route object: none | 147.160.144.0/24 | Route objects for it name AS398151. Add a route object with origin AS32768 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS32768 whose prefix no peer sees AS32768 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 63.169.52.128/25 | NTTCOM | No ROA |
| 63.171.143.128/25 | NTTCOM | No ROA |
| 63.172.252.0/22 | NTTCOM | No ROA |
| 65.39.128.0/18 | RADB | No ROA |
| 65.39.204.0/22 | RADB | No ROA |
| 65.39.212.0/22 | RADB | No ROA |
| 65.168.149.0/24 | NTTCOM | No ROA |
| 65.168.150.0/23 | NTTCOM | No ROA |
| 160.206.141.0/24 | RADB | No ROA |
| 196.1.26.0/23 | RADB | No ROA |
| 196.1.26.0/24 | RADB | No ROA |
| 196.1.27.0/24 | RADB | No ROA |
| 204.248.180.0/25 | NTTCOM | No ROA |
| 216.168.129.0/24 | ALTDB | No ROA |
| 216.168.130.0/24 | ALTDB | No ROA |
| 216.168.135.0/24 | ALTDB | No ROA |
| 219.83.128.0/21 | RADB | No ROA |
| 219.83.128.0/22 | RADB | No ROA |
| 219.83.132.0/22 | RADB | No ROA |
| 219.83.136.0/22 | RADB | No ROA |
| 219.83.140.0/22 | RADB | No ROA |
| 219.83.144.0/22 | RADB | No ROA |
| 219.83.148.0/22 | RADB | No ROA |
| 219.83.152.0/22 | RADB | No ROA |
| 219.83.156.0/22 | RADB | No ROA |
| 219.83.160.0/22 | RADB | No ROA |
| 219.83.164.0/22 | RADB | No ROA |
| 219.83.168.0/22 | RADB | No ROA |
| 219.83.172.0/22 | RADB | No ROA |
| 219.83.176.0/22 | RADB | No ROA |
| 219.83.180.0/22 | RADB | No ROA |
| 219.83.184.0/22 | RADB | No ROA |
| 219.83.188.0/22 | RADB | No ROA |
| 219.83.192.0/21 | RADB | No ROA |
| 219.83.192.0/22 | RADB | No ROA |
| 219.83.196.0/22 | RADB | No ROA |
| 219.83.200.0/21 | RADB | No ROA |
| 219.83.200.0/22 | RADB | No ROA |
| 219.83.204.0/22 | RADB | No ROA |
| 219.83.208.0/21 | RADB | No ROA |
| 219.83.208.0/22 | RADB | No ROA |
| 219.83.212.0/22 | RADB | No ROA |
| 219.83.216.0/21 | RADB | No ROA |
| 219.83.216.0/22 | RADB | No ROA |
| 219.83.220.0/22 | RADB | No ROA |
| 219.83.224.0/21 | RADB | No ROA |
| 219.83.224.0/22 | RADB | No ROA |
| 219.83.228.0/22 | RADB | No ROA |
| 219.83.232.0/21 | RADB | No ROA |
| 219.83.232.0/22 | RADB | No ROA |
| 219.83.236.0/22 | RADB | No ROA |
| 219.83.240.0/21 | RADB | No ROA |
| 219.83.240.0/22 | RADB | No ROA |
| 219.83.244.0/22 | RADB | No ROA |
| 219.83.248.0/21 | RADB | No ROA |
| 219.83.248.0/22 | RADB | No ROA |
| 219.83.252.0/22 | RADB | 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.