bgpreport

Network · data from 2026-11-12

AS55653 Skyline Semesta

Registry name: SKYLINE-AS-ID - Skyline Semesta, PT, ID · PeeringDB

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

Announced routes

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

202.10.63.0/24 Valid None 672 100% 69
43.249.140.0/22 Valid Other IRR onlyNTTCOM, RADB 673 100% 69
43.249.140.0/24 Valid Other IRR onlyNTTCOM, RADB 673 100% 68
43.249.141.0/24 Valid Other IRR onlyNTTCOM, RADB 673 100% 68
43.249.143.0/24 Valid Other IRR onlyNTTCOM, RADB 673 100% 68
103.11.96.0/22 Valid Other IRR onlyNTTCOM, RADB 673 100% 69
202.52.12.0/22 Valid Other IRR onlyNTTCOM, RADB 673 100% 69
14.102.152.0/22 Valid Other IRR onlyRADB 672 100% 69
14.102.153.0/24 Valid Other IRR onlyRADB 672 100% 69
14.102.154.0/24 Valid Other IRR onlyRADB 672 100% 69
14.102.155.0/24 Valid Other IRR onlyRADB 672 100% 69
43.249.142.0/24 Valid Other IRR onlyNTTCOM, RADB 672 100% 68
103.254.126.0/23 Valid Other IRR onlyRADB 672 100% 69
103.254.126.0/24 Valid Other IRR onlyRADB 672 100% 69
103.254.127.0/24 Valid Other IRR onlyRADB 672 100% 69
2402:c300::/32 Valid Other IRR onlyRADB 635 100% 70
103.11.96.0/23 Valid Other IRR onlyRADB 2 0%low visibility 3
103.11.98.0/23 Valid Other IRR onlyNTTCOM, RADB 2 0%low visibility 3
103.11.96.0/24 Valid RIR databaseAPNIC, RADB 673 100% 69
103.11.97.0/24 Valid RIR databaseAPNIC, RADB 673 100% 69
103.11.98.0/24 Valid RIR databaseAPNIC, RADB 673 100% 69
103.11.99.0/24 Valid RIR databaseAPNIC, RADB 673 100% 69
202.52.13.0/24 Valid RIR databaseAPNIC, RADB 673 100% 69
202.52.14.0/24 Valid RIR databaseAPNIC, RADB 673 100% 69
202.52.15.0/24 Valid RIR databaseAPNIC, RADB 673 100% 69
202.52.12.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
14.102.152.0/24 Valid RIR databaseAPNIC, RADB 35 5%low visibility 29

AS-SET

PeeringDB's irr_as_set for AS55653: AS55653. 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 (AS55653 isn't in the set, or no route object for AS55653 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 objectsAS55653 in itNot covered
AS55653 A single AS number, not a set: AS55653 (this network), 32 route objects.

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

  • Route object: none1
  • Route object: RIR17
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
Route object: none202.10.63.0/24No route object for it. Add a route object with origin AS55653 in the RIR database for the space.672 of 673
Route object: RIR43.249.140.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR43.249.140.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR43.249.141.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR43.249.143.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.11.96.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR202.52.12.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR14.102.152.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR14.102.153.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR14.102.154.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR14.102.155.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR43.249.142.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.254.126.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.254.126.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.254.127.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR2402:c300::/32Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR103.11.96.0/23Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR103.11.98.0/23Route object only in NTTCOM, RADB. Add it in the RIR database for the space.2 of 673

Route objects not announced

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

14.102.152.0/23NTTCOM, RADBValid
14.102.154.0/23RADBValid
43.249.140.0/23NTTCOMValid
43.249.142.0/23NTTCOMValid
202.52.12.0/23NTTCOM, RADBValid
202.52.14.0/23NTTCOM, RADBValid

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.