Network · data from 2026-11-12
AS399861 MOBITE-NET - Mobite Network LLC
Registry name: MOBITE-NET - Mobite Network LLC, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS399861, 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.191.248.0/24 | Valid | None | 670 100% |
| 2602:f7d6::/36 | Valid | Other origin only | 632 99% |
| 23.129.124.0/24 | Valid | RIR databaseARIN | 670 100% |
| 23.129.236.0/24 | Valid | RIR databaseARIN | 670 100% |
| 23.130.20.0/24 | Valid | RIR databaseARIN | 670 100% |
| 23.130.228.0/24 | Valid | RIR databaseARIN | 670 100% |
| 23.130.236.0/24 | Valid | RIR databaseARIN | 670 100% |
| 23.130.252.0/24 | Valid | RIR databaseARIN | 670 100% |
| 23.131.4.0/24 | Valid | RIR databaseARIN | 670 100% |
| 23.131.28.0/24 | Valid | RIR databaseARIN | 670 100% |
| 23.131.44.0/24 | Valid | RIR databaseARIN | 670 100% |
| 23.131.124.0/24 | Valid | RIR databaseARIN | 670 100% |
| 23.131.244.0/24 | Valid | RIR databaseARIN | 670 100% |
| 23.132.188.0/24 | Valid | RIR databaseARIN | 670 100% |
| 23.133.196.0/24 | Valid | RIR databaseARIN | 670 100% |
| 23.134.148.0/24 | Valid | RIR databaseARIN | 670 100% |
| 72.14.137.0/24 | Valid | RIR databaseARIN, RADB | 670 100% |
| 107.173.8.0/24 | Valid | RIR databaseARIN, RADB | 670 100% |
| 160.187.114.0/23 | Valid | RIR databaseAPNIC | 670 100% |
| 160.187.162.0/23 | Valid | RIR databaseAPNIC | 670 100% |
| 23.128.252.0/24 | Valid | RIR databaseARIN | 3 0%low visibility |
| 23.134.244.0/24 | Valid | RIR databaseARIN | 3 0%low visibility |
| 23.135.36.0/24 | Valid | RIR databaseARIN | 3 0%low visibility |
| 160.191.102.0/23 | Valid | RIR databaseAPNIC | 2 0%low visibility |
| 161.248.88.0/23 | Valid | RIR databaseAPNIC | 1 0%low visibility |
AS-SET
AS399861 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 9 are in fix.csv.
- Route object: none2
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 23.191.248.0/24 | No route object for it. Add a route object with origin AS399861 in the RIR database for the space. |
| Route object: none | 2602:f7d6::/36 | Route objects for it name AS401561. Add a route object with origin AS399861 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS399861 whose prefix no peer sees AS399861 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 23.128.180.0/24 | ARIN | Valid |
| 160.191.156.0/23 | APNIC | Valid |
| 192.227.201.0/24 | ARIN, RADB | Valid |
| 2001:470:338::/48 | ARIN | Valid |
| 2001:470:48c::/48 | ARIN | Valid |
| 2401:d320::/32 | APNIC | Valid |
| 2602:f705::/36 | ARIN | 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.