bgpreport

Network · data from 2026-11-12

AS45781 ToI-BN - NB-IoT

Registry name: ToI-BN - NB-IoT, TH · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS45781, 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.
2001:44c8:3120::/48 Valid Nonecovered by 2001:44c8:3100::/40 634 100% 68
2001:44c8:3121::/48 Valid Nonecovered by 2001:44c8:3100::/40 634 100% 68
110.49.201.0/24 Valid Other IRR onlyRADB 672 100% 66
119.31.105.0/24 Valid Other IRR onlyRADB 672 100% 66
119.31.106.0/24 Valid Other IRR onlyRADB 672 100% 66
119.31.107.0/24 Valid Other IRR onlyRADB 672 100% 66
119.31.119.0/24 Valid Other IRR onlyRADB 672 100% 66
2001:44c8:2000::/48 Valid Other IRR onlyRADB 634 100% 68
2001:44c8:3100::/40 Valid Other IRR onlyRADB 634 100% 68
119.31.104.0/24 Valid Other IRR onlyRADB 1 0%low visibility 1

AS-SET

AS45781 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 27 are in fix.csv.

  • Route object: none2
  • Route object: RIR8
  • Route object: not announced17
ChangePrefix or setDetailFull-table peers
Route object: none2001:44c8:3120::/48No route object for it. A route object for 2001:44c8:3100::/40 with origin AS45781 covers it (filters allowing more-specifics accept it). Add a route object with origin AS45781 in the RIR database for the space.634 of 636
Route object: none2001:44c8:3121::/48No route object for it. A route object for 2001:44c8:3100::/40 with origin AS45781 covers it (filters allowing more-specifics accept it). Add a route object with origin AS45781 in the RIR database for the space.634 of 636
Route object: RIR110.49.201.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR119.31.105.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR119.31.106.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR119.31.107.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR119.31.119.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR2001:44c8:2000::/48Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2001:44c8:3100::/40Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR119.31.104.0/24Route object only in RADB. Add it in the RIR database for the space.1 of 673

Route objects not announced

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

2001:44c8:2001::/48RADBValid
2001:44c8:3000::/36RADBValid
2001:44c8:3000::/40RADBValid
2001:44c8:3200::/40RADBValid
2001:44c8:3300::/40RADBValid
2001:44c8:3400::/40RADBValid
2001:44c8:3500::/40RADBValid
2001:44c8:3600::/40RADBValid
2001:44c8:3700::/40RADBValid
2001:44c8:3800::/40RADBValid
2001:44c8:3900::/40RADBValid
2001:44c8:3a00::/40RADBValid
2001:44c8:3b00::/40RADBValid
2001:44c8:3c00::/40RADBValid
2001:44c8:3d00::/40RADBValid
2001:44c8:3e00::/40RADBValid
2001:44c8:3f00::/40RADBValid

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.