bgpreport

Network · data from 2026-11-12

AS53187 UNICAMP

Registry name: AS53187 - UNIVERSIDADE ESTADUAL DE CAMPINAS, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS53187, 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.8.96.0/20 Valid Other IRR onlyRADB, TC 669 99% 68
143.106.0.0/16 Valid Other IRR onlyRADB, TC 668 99% 68
177.220.0.0/17 Valid Other IRR onlyRADB, TC 668 99% 68
2801:8a::/32 Valid Other IRR onlyRADB, TC 635 100% 70

AS-SET

PeeringDB's irr_as_set for AS53187: AS53187:RS-ROUTES. 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 (AS53187 isn't in the set, or no route object for AS53187 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 objectsAS53187 in itNot covered
AS53187:RS-ROUTES A route-set, not an AS-SET; route-sets aren't expanded.

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

  • Route object: RIR4
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
Route object: RIR177.8.96.0/20Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR143.106.0.0/16Route object only in RADB, TC. Add it in the RIR database for the space.668 of 673
Route object: RIR177.220.0.0/17Route object only in RADB, TC. Add it in the RIR database for the space.668 of 673
Route object: RIR2801:8a::/32Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

143.106.0.0/17TCValid
143.106.128.0/17TCValid
177.8.96.0/21TCValid
177.8.104.0/21TCValid
177.220.0.0/18TCValid
177.220.64.0/18TCValid
2801:8a::/33TCValid
2801:8a:8000::/33TCValid

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.