bgpreport

Network · data from 2026-11-12

AS45706 Tele Globe Global, PT

Registry name: TGG-AS-ID - Tele Globe Global, PT, ID · PeeringDB

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

Announced routes

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

103.145.220.0/23 Valid None 672 100% 69
103.145.220.0/24 Valid None 672 100% 69
103.145.221.0/24 Valid None 672 100% 69
2406:a300::/32 Valid None 1 0%low visibility 2
103.244.216.0/23 Valid Other IRR onlyRADB 672 100% 69
103.244.216.0/24 Valid Other IRR onlyRADB 672 100% 69
103.244.217.0/24 Valid Other IRR onlyRADB 672 100% 69
150.107.250.0/24 Valid Other IRR onlyRADB 671 100% 69
150.107.251.0/24 Valid Other IRR onlyRADB 671 100% 69
103.18.28.0/24 Valid Other IRR onlyNTTCOM, RADB 634 94% 68
103.18.29.0/24 Valid Other IRR onlyNTTCOM, RADB 634 94% 68
103.18.30.0/24 Valid Other IRR onlyNTTCOM, RADB 634 94% 68
103.18.31.0/24 Valid Other IRR onlyNTTCOM, RADB 634 94% 68
27.123.0.0/24 Valid Other IRR onlyNTTCOM, RADB 633 94% 68
27.123.1.0/24 Valid Other IRR onlyNTTCOM, RADB 633 94% 68
27.123.2.0/24 Valid Other IRR onlyRADB 633 94% 68
27.123.3.0/24 Valid Other IRR onlyRADB 633 94% 68
27.123.4.0/24 Valid Other IRR onlyRADB 633 94% 68
27.123.5.0/24 Valid Other IRR onlyRADB 633 94% 68
27.123.6.0/24 Valid Other IRR onlyRADB 633 94% 68
27.123.7.0/24 Valid Other IRR onlyRADB 633 94% 68
150.107.248.0/24 Valid Other IRR onlyRADB 628 93% 68
150.107.249.0/24 Valid Other IRR onlyRADB 627 93% 68
150.107.248.0/22 Valid RIR databaseAPNIC, RADB 671 100% 69
202.43.114.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 579 86% 66
202.43.115.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 579 86% 66
103.18.28.0/22 Valid RIR databaseAPNIC, RADB 543 81% 68
27.123.0.0/21 Valid RIR databaseAPNIC, NTTCOM, RADB 430 64% 67
202.43.114.0/23 Valid RIR databaseAPNIC, NTTCOM, RADB 345 51% 62

AS-SET

AS45706's PeeringDB record names no 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 32 are in fix.csv.

  • Route object: none4
  • Route object: RIR19
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
Route object: none103.145.220.0/23No route object for it. Add a route object with origin AS45706 in the RIR database for the space.672 of 673
Route object: none103.145.220.0/24No route object for it. Add a route object with origin AS45706 in the RIR database for the space.672 of 673
Route object: none103.145.221.0/24No route object for it. Add a route object with origin AS45706 in the RIR database for the space.672 of 673
Route object: none2406:a300::/32No route object for it. Add a route object with origin AS45706 in the RIR database for the space.1 of 636
Route object: RIR103.244.216.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.244.216.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.244.217.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR150.107.250.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR150.107.251.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR103.18.28.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.634 of 673
Route object: RIR103.18.29.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.634 of 673
Route object: RIR103.18.30.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.634 of 673
Route object: RIR103.18.31.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.634 of 673
Route object: RIR27.123.0.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.633 of 673
Route object: RIR27.123.1.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.633 of 673
Route object: RIR27.123.2.0/24Route object only in RADB. Add it in the RIR database for the space.633 of 673
Route object: RIR27.123.3.0/24Route object only in RADB. Add it in the RIR database for the space.633 of 673
Route object: RIR27.123.4.0/24Route object only in RADB. Add it in the RIR database for the space.633 of 673
Route object: RIR27.123.5.0/24Route object only in RADB. Add it in the RIR database for the space.633 of 673
Route object: RIR27.123.6.0/24Route object only in RADB. Add it in the RIR database for the space.633 of 673
Route object: RIR27.123.7.0/24Route object only in RADB. Add it in the RIR database for the space.633 of 673
Route object: RIR150.107.248.0/24Route object only in RADB. Add it in the RIR database for the space.628 of 673
Route object: RIR150.107.249.0/24Route object only in RADB. Add it in the RIR database for the space.627 of 673

Route objects not announced

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

27.123.0.0/22NTTCOMValid
27.123.0.0/23NTTCOM, RADBValid
27.123.2.0/23RADBValid
27.123.4.0/23RADBValid
27.123.6.0/23RADBValid
103.18.28.0/23RADBValid
103.18.30.0/23RADBValid
150.107.248.0/23RADBValid
150.107.250.0/23RADBValid

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.