bgpreport

Network · data from 2026-11-12

AS136201 BGUS-AS-AP - BG UNIFIED SOLUTIONS PTY LTD

Registry name: BGUS-AS-AP - BG UNIFIED SOLUTIONS PTY LTD, AU · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS136201, 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.5.184.0/24 No ROA Other IRR onlyRADB 669 99% 67
103.83.102.0/24 No ROA RIR databaseAPNIC, NTTCOM 669 99% 67
103.108.222.0/23 No ROA RIR databaseAPNIC, NTTCOM, RADB 669 99% 67
103.117.63.0/24 No ROA RIR databaseAPNIC, NTTCOM, RADB 669 99% 67

AS-SET

AS136201 isn't in PeeringDB, where networks name their 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 7 are in fix.csv.

  • ROA: none4
  • Route object: RIR1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none202.5.184.0/24No ROA covers it. Add a ROA for AS136201, maxLength 24.669 of 673
Route object: RIR202.5.184.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none103.83.102.0/24No ROA covers it. Add a ROA for AS136201, maxLength 24.669 of 673
ROA: none103.108.222.0/23No ROA covers it. Add a ROA for AS136201, maxLength 23.669 of 673
ROA: none103.117.63.0/24No ROA covers it. Add a ROA for AS136201, maxLength 24.669 of 673

Route objects not announced

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

103.108.223.0/24APNIC, NTTCOM, RADBNo ROA
2001:df0:4100::/48NTTCOMNo ROA

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.