bgpreport

Network · data from 2026-11-12

AS52547

Not in the RIR AS name list · not in PeeringDB

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

Announced routes

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

177.152.176.0/21 Valid Other IRR onlyRADB 0 0%low visibility 1
177.152.176.0/22 Valid Other IRR onlyRADB 0 0%low visibility 1
177.152.180.0/22 Valid Other IRR onlyRADB 0 0%low visibility 1

AS-SET

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

  • Route object: RIR3
  • Route object: not announced48
ChangePrefix or setDetailFull-table peers
Route object: RIR177.152.176.0/21Route object only in RADB. Add it in the RIR database for the space.0 of 673
Route object: RIR177.152.176.0/22Route object only in RADB. Add it in the RIR database for the space.0 of 673
Route object: RIR177.152.180.0/22Route object only in RADB. Add it in the RIR database for the space.0 of 673

Route objects not announced

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

170.233.52.0/22RADBValid
170.233.52.0/23RADBValid
170.233.52.0/24RADBValid
170.233.53.0/24RADBValid
170.233.54.0/23RADBValid
170.233.54.0/24RADBValid
170.233.55.0/24RADBValid
177.152.176.0/23RADBValid
177.152.176.0/24RADBValid
177.152.177.0/24RADBValid
177.152.178.0/23RADBValid
177.152.178.0/24RADBValid
177.152.179.0/24RADBValid
177.152.180.0/23RADBValid
177.152.180.0/24RADBValid
177.152.181.0/24RADBValid
177.152.182.0/23RADBValid
177.152.182.0/24RADBValid
177.152.183.0/24RADBValid
200.11.8.0/21RADBValid
200.11.8.0/22RADBValid
200.11.8.0/23RADBValid
200.11.8.0/24RADBValid
200.11.9.0/24RADBValid
200.11.10.0/23RADBValid
200.11.10.0/24RADBValid
200.11.11.0/24RADBValid
200.11.12.0/22RADBValid
200.11.12.0/23RADBValid
200.11.12.0/24RADBValid
200.11.13.0/24RADBValid
200.11.14.0/23RADBValid
200.11.14.0/24RADBValid
200.11.15.0/24RADBValid
2804:e28::/32RADBValid
2804:e28::/33RADBValid
2804:e28::/34RADBValid
2804:e28::/36RADBValid
2804:e28::/44RADBValid
2804:e28:20::/44RADBValid
2804:e28:60::/44RADBValid
2804:e28:80::/42RADBValid
2804:e28:e0::/44RADBValid
2804:e28:f0::/44RADBValid
2804:e28:4000::/34RADBValid
2804:e28:8000::/33RADBValid
2804:e28:8000::/34RADBValid
2804:e28:c000::/34RADBValid

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.