bgpreport

Network · data from 2026-11-12

AS211421 MOBINONE Asiatech Data Transmission company

Registry name: MOBINONE Asiatech Data Transmission company, IR · not in PeeringDB

10IPv4 routes 100.0% RPKI valid · 60.0% with a route object
2IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 4 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
6Route objects not announced registered with origin AS211421, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS211421, 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.

152.89.46.0/24 Valid Nonecovered by 152.89.44.0/22 672 100% 66
152.89.44.0/24 Valid Nonecovered by 152.89.44.0/22 671 100% 66
152.89.45.0/24 Valid Other origin onlycovered by 152.89.44.0/22 671 100% 66
152.89.47.0/24 Valid Other origin onlycovered by 152.89.44.0/22 671 100% 66
80.249.112.0/23 Valid RIR databaseRIPE 671 100% 66
94.184.9.0/24 Valid RIR databaseRIPE 671 100% 66
94.184.15.0/24 Valid RIR databaseRIPE 671 100% 66
94.184.26.0/24 Valid RIR databaseRIPE 671 100% 66
213.109.199.0/24 Valid RIR databaseRIPE 671 100% 66
94.184.16.0/24 Valid RIR databaseRIPE 670 100% 66
2a03:9381:10::/48 Valid RIR databaseRIPE 635 100% 67
2a03:9381:9::/48 Valid RIR databaseRIPE 634 100% 67

AS-SET

AS211421 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 10 are in fix.csv.

  • Route object: none4
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
Route object: none152.89.46.0/24No route object for it. A route object for 152.89.44.0/22 with origin AS211421 covers it (filters allowing more-specifics accept it). Add a route object with origin AS211421 in the RIR database for the space.672 of 673
Route object: none152.89.44.0/24No route object for it. A route object for 152.89.44.0/22 with origin AS211421 covers it (filters allowing more-specifics accept it). Add a route object with origin AS211421 in the RIR database for the space.671 of 673
Route object: none152.89.45.0/24Route objects for it name AS48715. A route object for 152.89.44.0/22 with origin AS211421 covers it (filters allowing more-specifics accept it). Add a route object with origin AS211421 in the RIR database for the space.671 of 673
Route object: none152.89.47.0/24Route objects for it name AS48715. A route object for 152.89.44.0/22 with origin AS211421 covers it (filters allowing more-specifics accept it). Add a route object with origin AS211421 in the RIR database for the space.671 of 673

Route objects not announced

Route objects with origin AS211421 whose prefix no peer sees AS211421 announce. Many are kept on purpose (backup routes, space announced only in some places).

94.184.14.0/24RIPEValid
94.184.37.0/24RIPEValid
152.89.44.0/22RIPEValid
176.117.107.0/24RIPEInvalid: origin
185.81.97.0/24RIPEValid
194.59.170.0/24RIPEValid

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.