bgpreport

Network · data from 2026-11-12

AS59365 Southlink Communication

Registry name: BD-NETWORKS-AS-AP - BD Networks, BD · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS59365, 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.183.16.0/24 Invalid: origin Other origin only 0 0%low visibility 1
103.231.228.0/22 No ROA None 0 0%low visibility 1
103.231.228.0/23 No ROA None 0 0%low visibility 1
103.231.230.0/23 No ROA None 0 0%low visibility 1
103.231.228.0/24 Valid RIR databaseAPNIC 673 100% 69
103.231.229.0/24 Valid RIR databaseAPNIC 673 100% 67
103.231.230.0/24 Valid RIR databaseAPNIC 673 100% 67
103.231.231.0/24 Valid RIR databaseAPNIC 673 100% 69
157.119.48.0/24 Valid RIR databaseAPNIC 673 100% 67
157.119.49.0/24 Valid RIR databaseAPNIC 673 100% 69
157.119.50.0/24 Valid RIR databaseAPNIC 673 100% 67
157.119.51.0/24 Valid RIR databaseAPNIC 673 100% 67
157.119.48.0/22 Valid RIR databaseAPNIC 0 0%low visibility 1
157.119.48.0/23 Valid RIR databaseAPNIC 0 0%low visibility 1
157.119.50.0/23 Valid RIR databaseAPNIC 0 0%low visibility 1

AS-SET

AS59365'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 9 are in fix.csv.

  • ROA: origin1
  • ROA: none3
  • Route object: none4
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: origin103.183.16.0/24ROAs covering it name AS149633, not AS59365. If AS59365 should announce it, add a ROA for AS59365.0 of 673
Route object: none103.183.16.0/24Route objects for it name AS149633. Add a route object with origin AS59365 in the RIR database for the space.0 of 673
ROA: none103.231.228.0/22No ROA covers it. Add a ROA for AS59365, maxLength 22.0 of 673
Route object: none103.231.228.0/22No route object for it. Add a route object with origin AS59365 in the RIR database for the space.0 of 673
ROA: none103.231.228.0/23No ROA covers it. Add a ROA for AS59365, maxLength 23.0 of 673
Route object: none103.231.228.0/23No route object for it. Add a route object with origin AS59365 in the RIR database for the space.0 of 673
ROA: none103.231.230.0/23No ROA covers it. Add a ROA for AS59365, maxLength 23.0 of 673
Route object: none103.231.230.0/23No route object for it. Add a route object with origin AS59365 in the RIR database for the space.0 of 673

Route objects not announced

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

2404:4b80::/32APNICValid

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.