bgpreport

Network · data from 2026-11-12

AS53166 UNESP

Registry name: AS53166 - UNIVERSIDADE ESTADUAL PAULISTA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS53166, 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.
186.217.167.0/24 Valid Nonecovered by 186.217.0.0/16 669 99% 68
2801:88::/33 Valid Nonecovered by 2801:88::/32 635 100% 68
2801:88:8000::/33 Valid Nonecovered by 2801:88::/32 635 100% 68
186.217.0.0/16 Valid Other IRR onlyRADB, TC 668 99% 68
200.145.0.0/16 Valid Other IRR onlyRADB, TC 667 99% 68
2801:88::/32 Valid Other IRR onlyRADB, TC 635 100% 70

AS-SET

PeeringDB's irr_as_set for AS53166: AS53166:AS-ANNOUNCEMENTS. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS53166 isn't in the set, or no route object for AS53166 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS53166 in itNot covered
AS53166:AS-ANNOUNCEMENTS TC 123 Yes 0

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

  • Route object: none3
  • Route object: RIR3
ChangePrefix or setDetailFull-table peers
Route object: none186.217.167.0/24No route object for it. A route object for 186.217.0.0/16 with origin AS53166 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53166 in the RIR database for the space.669 of 673
Route object: none2801:88::/33No route object for it. A route object for 2801:88::/32 with origin AS53166 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53166 in the RIR database for the space.635 of 636
Route object: none2801:88:8000::/33No route object for it. A route object for 2801:88::/32 with origin AS53166 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53166 in the RIR database for the space.635 of 636
Route object: RIR186.217.0.0/16Route object only in RADB, TC. Add it in the RIR database for the space.668 of 673
Route object: RIR200.145.0.0/16Route object only in RADB, TC. Add it in the RIR database for the space.667 of 673
Route object: RIR2801:88::/32Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636

Route objects not announced

Every route object with origin AS53166 is announced.

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.