bgpreport

Network · data from 2026-11-12

AS61209 USB-AS University of Sistan and Baluchestan

Registry name: USB-AS University of Sistan and Baluchestan, IR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS61209, 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.
80.191.172.0/24 Invalid: maxLength Nonecovered by 80.191.172.0/23 93 14% 37
80.191.173.0/24 Invalid: maxLength Nonecovered by 80.191.172.0/23 0 0%low visibility 1
79.127.64.0/24 Valid RIR databaseRIPE 671 100% 66
87.107.186.0/24 Valid RIR databaseRIPE 671 100% 66
80.191.172.0/23 Valid RIR databaseRIPE 670 100% 66

AS-SET

AS61209 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: maxLength2
  • Route object: none2
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: maxLength80.191.172.0/24ROA 80.191.172.0/23 AS61209 has maxLength 23; the route is a /24. Raise the maxLength, or add a ROA for 80.191.172.0/24.93 of 673
Route object: none80.191.172.0/24No route object for it. A route object for 80.191.172.0/23 with origin AS61209 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61209 in the RIR database for the space.93 of 673
ROA: maxLength80.191.173.0/24ROA 80.191.172.0/23 AS61209 has maxLength 23; the route is a /24. Raise the maxLength, or add a ROA for 80.191.173.0/24.0 of 673
Route object: none80.191.173.0/24No route object for it. A route object for 80.191.172.0/23 with origin AS61209 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61209 in the RIR database for the space.0 of 673

Route objects not announced

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

2.181.132.0/22RIPEInvalid: origin
46.209.184.0/23RIPEInvalid: origin
46.209.184.0/24RIPEInvalid: origin

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.