bgpreport

Network · data from 2026-11-12

AS52888 UFSCar - Universidade Federal de São Carlos

Registry name: AS52888 - UNIVERSIDADE FEDERAL DE SAO CARLOS, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS52888, 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.219.92.0/22 Valid Nonecovered by 186.219.80.0/20 672 100% 68
200.18.103.0/24 Valid Nonecovered by 200.18.96.0/21 671 100% 68
200.136.248.0/22 Valid Nonecovered by 200.136.192.0/18 671 100% 68
186.219.88.0/22 Valid Nonecovered by 186.219.80.0/20 669 99% 68
200.136.190.0/24 Valid Nonecovered by 200.136.190.0/23 668 99% 68
200.136.191.0/24 Valid Nonecovered by 200.136.190.0/23 668 99% 68
2801:b0::/33 Valid Nonecovered by 2801:b0::/32 635 100% 70
2801:b0:8000::/33 Valid Nonecovered by 2801:b0::/32 635 100% 70
200.18.96.0/22 Valid Nonecovered by 200.18.96.0/21 147 22% 47
200.18.100.0/22 Valid Nonecovered by 200.18.96.0/21 147 22% 47
200.136.192.0/19 Valid Nonecovered by 200.136.192.0/18 147 22% 47
200.136.224.0/19 Valid Nonecovered by 200.136.192.0/18 147 22% 47
186.219.80.0/21 Valid Nonecovered by 186.219.80.0/20 146 22% 47
186.219.88.0/21 Valid Nonecovered by 186.219.80.0/20 146 22% 47
200.133.224.0/21 Valid Nonecovered by 200.133.224.0/20 146 22% 47
200.18.104.0/24 Valid Nonecovered by 200.18.104.0/23 145 22% 47
200.18.105.0/24 Valid Nonecovered by 200.18.104.0/23 145 22% 47
200.133.232.0/21 Valid Nonecovered by 200.133.224.0/20 145 22% 47
186.219.80.0/20 Valid Other IRR onlyRADB, TC 672 100% 68
200.18.96.0/21 Valid Other IRR onlyRADB 671 100% 68
200.18.96.0/24 Valid Other IRR onlyRADB 671 100% 68
200.18.104.0/23 Valid Other IRR onlyRADB 671 100% 68
200.133.224.0/20 Valid Other IRR onlyRADB, TC 671 100% 68
200.133.236.0/23 Valid Other IRR onlyTC 671 100% 68
200.136.189.0/24 Valid Other IRR onlyRADB 671 100% 68
200.136.192.0/18 Valid Other IRR onlyRADB 671 100% 68
200.9.84.0/24 Valid Other IRR onlyRADB, TC 668 99% 68
200.18.102.0/24 Valid Other IRR onlyRADB 668 99% 68
200.133.238.0/23 Valid Other IRR onlyTC 668 99% 68
200.136.190.0/23 Valid Other IRR onlyRADB 668 99% 68
2801:b0::/32 Valid Other IRR onlyRADB, TC 635 100% 70
2801:b0:b0::/46 Valid Other IRR onlyTC 635 100% 70
2801:b0:c0::/46 Valid Other IRR onlyTC 635 100% 70
2801:b0:d0::/46 Valid Other IRR onlyTC 635 100% 70

AS-SET

PeeringDB's irr_as_set for AS52888: AS52888. 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 (AS52888 isn't in the set, or no route object for AS52888 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 objectsAS52888 in itNot covered
AS52888 A single AS number, not a set: AS52888 (this network), 18 route objects.

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

  • Route object: none18
  • Route object: RIR16
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
Route object: none186.219.92.0/22No route object for it. A route object for 186.219.80.0/20 with origin AS52888 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52888 in the RIR database for the space.672 of 673
Route object: none200.18.103.0/24No route object for it. A route object for 200.18.96.0/21 with origin AS52888 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52888 in the RIR database for the space.671 of 673
Route object: none200.136.248.0/22No route object for it. A route object for 200.136.192.0/18 with origin AS52888 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52888 in the RIR database for the space.671 of 673
Route object: none186.219.88.0/22No route object for it. A route object for 186.219.80.0/20 with origin AS52888 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52888 in the RIR database for the space.669 of 673
Route object: none200.136.190.0/24No route object for it. A route object for 200.136.190.0/23 with origin AS52888 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52888 in the RIR database for the space.668 of 673
Route object: none200.136.191.0/24No route object for it. A route object for 200.136.190.0/23 with origin AS52888 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52888 in the RIR database for the space.668 of 673
Route object: none2801:b0::/33No route object for it. A route object for 2801:b0::/32 with origin AS52888 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52888 in the RIR database for the space.635 of 636
Route object: none2801:b0:8000::/33No route object for it. A route object for 2801:b0::/32 with origin AS52888 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52888 in the RIR database for the space.635 of 636
Route object: none200.18.96.0/22No route object for it. A route object for 200.18.96.0/21 with origin AS52888 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52888 in the RIR database for the space.147 of 673
Route object: none200.18.100.0/22No route object for it. A route object for 200.18.96.0/21 with origin AS52888 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52888 in the RIR database for the space.147 of 673
Route object: none200.136.192.0/19No route object for it. A route object for 200.136.192.0/18 with origin AS52888 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52888 in the RIR database for the space.147 of 673
Route object: none200.136.224.0/19No route object for it. A route object for 200.136.192.0/18 with origin AS52888 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52888 in the RIR database for the space.147 of 673
Route object: none186.219.80.0/21No route object for it. A route object for 186.219.80.0/20 with origin AS52888 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52888 in the RIR database for the space.146 of 673
Route object: none186.219.88.0/21No route object for it. A route object for 186.219.80.0/20 with origin AS52888 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52888 in the RIR database for the space.146 of 673
Route object: none200.133.224.0/21No route object for it. A route object for 200.133.224.0/20 with origin AS52888 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52888 in the RIR database for the space.146 of 673
Route object: none200.18.104.0/24No route object for it. A route object for 200.18.104.0/23 with origin AS52888 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52888 in the RIR database for the space.145 of 673
Route object: none200.18.105.0/24No route object for it. A route object for 200.18.104.0/23 with origin AS52888 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52888 in the RIR database for the space.145 of 673
Route object: none200.133.232.0/21No route object for it. A route object for 200.133.224.0/20 with origin AS52888 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52888 in the RIR database for the space.145 of 673
Route object: RIR186.219.80.0/20Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR200.18.96.0/21Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR200.18.96.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR200.18.104.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR200.133.224.0/20Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR200.133.236.0/23Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR200.136.189.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR200.136.192.0/18Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR200.9.84.0/24Route object only in RADB, TC. Add it in the RIR database for the space.668 of 673
Route object: RIR200.18.102.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR200.133.238.0/23Route object only in TC. Add it in the RIR database for the space.668 of 673
Route object: RIR200.136.190.0/23Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR2801:b0::/32Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2801:b0:b0::/46Route object only in TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2801:b0:c0::/46Route object only in TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2801:b0:d0::/46Route object only in TC. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

200.18.100.0/23RADBValid
200.19.230.0/23RADBNo 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.