bgpreport

Network · data from 2026-11-12

AS59342 BBS-PH

Registry name: BBS-PH - ABSATELLITE BBS-PH, PH · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS59342, 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.252.176.0/22 No ROA Other IRR onlyRADB 6 1%low visibility 5
103.252.176.0/24 Valid Other IRR onlyRADB 673 100% 67
103.252.177.0/24 Valid Other IRR onlyRADB 673 100% 67
103.229.104.0/23 Valid Other IRR onlyRADB 671 100% 67
103.229.104.0/24 Valid Other IRR onlyRADB 671 100% 67
103.229.105.0/24 Valid Other IRR onlyRADB 671 100% 66
103.229.106.0/24 Valid Other IRR onlyRADB 671 100% 67
103.229.107.0/24 Valid Other IRR onlyRADB 671 100% 67
103.252.178.0/24 Valid Other IRR onlyRADB 669 99% 66
103.252.179.0/24 Valid Other IRR onlyRADB 669 99% 66
2400:bd40::/34 Valid Other IRR onlyRADB 636 100% 69
2400:bd40:4000::/34 Valid Other IRR onlyRADB 636 100% 69
2400:bd40:8000::/34 Valid Other IRR onlyRADB 636 100% 69
2400:bd40:c000::/34 Valid Other IRR onlyRADB 636 100% 69
103.229.104.0/22 Valid RIR databaseAPNIC, RADB 671 100% 67
103.229.106.0/23 Valid RIR databaseAPNIC 671 100% 67

AS-SET

AS59342'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 18 are in fix.csv.

  • ROA: none1
  • Route object: RIR14
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none103.252.176.0/22No ROA covers it. Add a ROA for AS59342, maxLength 22.6 of 673
Route object: RIR103.252.176.0/22Route object only in RADB. Add it in the RIR database for the space.6 of 673
Route object: RIR103.252.176.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.252.177.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.229.104.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR103.229.104.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR103.229.105.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR103.229.106.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR103.229.107.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR103.252.178.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR103.252.179.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR2400:bd40::/34Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2400:bd40:4000::/34Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2400:bd40:8000::/34Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2400:bd40:c000::/34Route object only in RADB. Add it in the RIR database for the space.636 of 636

Route objects not announced

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

103.252.176.0/23RADBNo ROA
103.252.178.0/23RADBNo ROA
2400:bd40::/32RADBValid

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.