bgpreport

Network · data from 2026-11-12

AS55900 GLBB Japan

Registry name: GLBB-JP - GLBB Japan KK, JP · PeeringDB

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

Announced routes

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

104.222.192.0/20 Valid Other IRR onlyRADB 673 100% 67
104.222.208.0/21 Valid Other IRR onlyRADB 673 100% 67
172.97.80.0/20 Valid Other IRR onlyRADB 673 100% 67
180.131.208.0/20 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
27.0.16.0/20 Valid Other IRR onlyNTTCOM, RADB 672 100% 67
103.250.92.0/24 Valid Other IRR onlyRADB 672 100% 67
103.250.93.0/24 Valid Other IRR onlyRADB 672 100% 67
109.236.0.0/20 Valid Other IRR onlyRADB 672 100% 67
137.220.16.0/20 Valid Other IRR onlyRADB 672 100% 67
180.131.210.0/24 Valid Other IRR onlyNTTCOM, RADB 672 100% 67
180.131.224.0/20 Valid Other IRR onlyNTTCOM, RADB 672 100% 67
180.131.240.0/20 Valid Other IRR onlyNTTCOM, RADB 672 100% 67
198.144.128.0/20 Valid Other IRR onlyNTTCOM, RADB 672 100% 67
202.171.224.0/21 Valid Other IRR onlyRADB 672 100% 67
218.223.128.0/21 Valid Other IRR onlyJPIRR, RADB 672 100% 67
103.7.88.0/22 Valid Other IRR onlyRADB 671 100% 67
104.222.216.0/22 Valid Other IRR onlyRADB 671 100% 67
123.100.136.0/22 Valid Other IRR onlyRADB 671 100% 67
123.100.156.0/22 Valid Other IRR onlyRADB 671 100% 67
27.0.31.0/24 Valid Other IRR onlyRADB 670 100% 67
43.248.160.0/22 Valid Other IRR onlyRADB 670 100% 67
103.13.248.0/22 Valid Other IRR onlyNTTCOM, RADB 670 100% 67
103.100.189.0/24 Valid Other IRR onlyRADB 670 100% 67
103.100.190.0/23 Valid Other IRR onlyRADB 670 100% 67
103.250.92.0/22 Valid Other IRR onlyRADB 670 100% 67
202.12.244.0/22 Valid Other IRR onlyRADB 670 100% 67
203.23.200.0/22 Valid Other IRR onlyRADB 670 100% 67
218.223.132.0/22 Valid Other IRR onlyJPIRR, RADB 670 100% 67
218.223.128.0/22 Valid Other IRR onlyJPIRR, RADB 669 99% 67
2404:2d00::/32 Valid Other IRR onlyNTTCOM, RADB 636 100% 67
202.12.246.0/24 Valid Other IRR onlyRADB 128 19% 47
202.171.224.0/22 Valid Other IRR onlyRADB 128 19% 47
180.131.224.0/19 Valid Other IRR onlyRADB 3 0%low visibility 1

AS-SET

PeeringDB's irr_as_set for AS55900: AS-GLBB-TRANSIT. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS55900 isn't in the set, or no route object for AS55900 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS55900 in itNot covered
AS-GLBB-TRANSIT RADBlists itself further down 25596,370 Yes 0

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

  • Route object: RIR33
  • Route object: not announced44
ChangePrefix or setDetailFull-table peers
Route object: RIR104.222.192.0/20Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR104.222.208.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR172.97.80.0/20Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR180.131.208.0/20Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR27.0.16.0/20Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.250.92.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.250.93.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR109.236.0.0/20Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR137.220.16.0/20Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR180.131.210.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR180.131.224.0/20Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR180.131.240.0/20Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR198.144.128.0/20Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR202.171.224.0/21Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR218.223.128.0/21Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.7.88.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR104.222.216.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR123.100.136.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR123.100.156.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR27.0.31.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR43.248.160.0/22Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR103.13.248.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR103.100.189.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR103.100.190.0/23Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR103.250.92.0/22Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR202.12.244.0/22Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR203.23.200.0/22Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR218.223.132.0/22Route object only in JPIRR, RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR218.223.128.0/22Route object only in JPIRR, RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR2404:2d00::/32Route object only in NTTCOM, RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR202.12.246.0/24Route object only in RADB. Add it in the RIR database for the space.128 of 673
Route object: RIR202.171.224.0/22Route object only in RADB. Add it in the RIR database for the space.128 of 673
Route object: RIR180.131.224.0/19Route object only in RADB. Add it in the RIR database for the space.3 of 673

Route objects not announced

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

27.0.16.0/21RADBValid
27.0.24.0/21RADBValid
27.0.24.0/22RADBValid
103.13.248.0/23RADBValid
103.13.250.0/23RADBValid
103.13.250.0/24RADBValid
103.13.251.0/24RADBValid
109.236.2.0/23RADBValid
137.220.21.0/24RADBValid
137.220.22.0/24RADBValid
137.220.26.0/24RADBValid
137.220.27.0/24RADBValid
137.220.30.0/24RADBValid
137.220.31.0/24RADBValid
180.131.208.0/21RADBValid
180.131.208.0/24RADBValid
180.131.209.0/24RADBValid
180.131.213.0/24RADBValid
180.131.216.0/21RADBValid
180.131.216.0/24RADBValid
180.131.221.0/24RADBValid
180.131.223.0/24RADBValid
180.131.224.0/21RADBValid
180.131.224.0/22RADBValid
180.131.232.0/21RADBValid
180.131.238.0/23RADBValid
180.131.240.0/21RADBValid
180.131.248.0/21RADBValid
198.144.128.0/21RADBValid
198.144.128.0/24RADBValid
198.144.129.0/24RADBValid
198.144.132.0/24RADBValid
198.144.134.0/24RADBValid
198.144.136.0/21RADBValid
198.144.136.0/24RADBValid
198.144.138.0/24RADBValid
202.12.244.0/24RADBValid
202.171.224.0/24RADBValid
202.171.225.0/24RADBValid
202.171.226.0/24RADBValid
202.171.227.0/24RADBValid
2404:2d00:4e00::/48RADBValid
2404:2d00:4e01::/48RADBValid
2404:2d00:5000::/36RADBValid

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.