bgpreport

Network · data from 2026-11-12

AS52686 F.J.FANTINI AMPARO ME

Registry name: AS52686 - F.J.FANTINI AMPARO ME, BR · PeeringDB

21IPv4 routes 100.0% RPKI valid · 100.0% with a route object
7IPv6 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
12Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS52686, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS52686, 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.
170.246.80.0/22 Valid Other IRR onlyTC 672 100% 67
177.67.156.0/22 Valid Other IRR onlyTC 672 100% 67
138.99.204.0/22 Valid Other IRR onlyTC 671 100% 67
2804:2440::/32 Valid Other IRR onlyTC 634 100% 67
2804:2440::/33 Valid Other IRR onlyTC 349 55% 65
2804:2440:8000::/33 Valid Other IRR onlyTC 349 55% 65
2804:2440::/34 Valid Other IRR onlyTC 323 51% 63
2804:2440:4000::/34 Valid Other IRR onlyTC 323 51% 63
2804:2440:8000::/34 Valid Other IRR onlyTC 323 51% 63
2804:2440:c000::/34 Valid Other IRR onlyTC 323 51% 63
170.246.80.0/23 Valid Other IRR onlyTC 205 30% 56
177.67.156.0/23 Valid Other IRR onlyTC 205 30% 56
138.99.204.0/23 Valid Other IRR onlyTC 204 30% 56
138.99.206.0/23 Valid Other IRR onlyTC 204 30% 56
170.246.82.0/23 Valid Other IRR onlyTC 204 30% 56
177.67.158.0/23 Valid Other IRR onlyTC 204 30% 56
138.99.204.0/24 Valid Other IRR onlyTC 24 4%low visibility 11
138.99.205.0/24 Valid Other IRR onlyTC 24 4%low visibility 11
138.99.206.0/24 Valid Other IRR onlyTC 24 4%low visibility 11
138.99.207.0/24 Valid Other IRR onlyTC 24 4%low visibility 11
170.246.80.0/24 Valid Other IRR onlyTC 24 4%low visibility 11
170.246.81.0/24 Valid Other IRR onlyTC 24 4%low visibility 11
170.246.82.0/24 Valid Other IRR onlyTC 24 4%low visibility 11
170.246.83.0/24 Valid Other IRR onlyTC 24 4%low visibility 11
177.67.156.0/24 Valid Other IRR onlyTC 24 4%low visibility 11
177.67.157.0/24 Valid Other IRR onlyTC 24 4%low visibility 11
177.67.158.0/24 Valid Other IRR onlyTC 24 4%low visibility 11
177.67.159.0/24 Valid Other IRR onlyTC 24 4%low visibility 11

AS-SET

PeeringDB's irr_as_set for AS52686: AS52686: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 (AS52686 isn't in the set, or no route object for AS52686 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 objectsAS52686 in itNot covered
AS52686:AS-ANNOUNCEMENTS TC 1228 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 28 are in fix.csv.

  • Route object: RIR28
ChangePrefix or setDetailFull-table peers
Route object: RIR170.246.80.0/22Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR177.67.156.0/22Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR138.99.204.0/22Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR2804:2440::/32Route object only in TC. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:2440::/33Route object only in TC. Add it in the RIR database for the space.349 of 636
Route object: RIR2804:2440:8000::/33Route object only in TC. Add it in the RIR database for the space.349 of 636
Route object: RIR2804:2440::/34Route object only in TC. Add it in the RIR database for the space.323 of 636
Route object: RIR2804:2440:4000::/34Route object only in TC. Add it in the RIR database for the space.323 of 636
Route object: RIR2804:2440:8000::/34Route object only in TC. Add it in the RIR database for the space.323 of 636
Route object: RIR2804:2440:c000::/34Route object only in TC. Add it in the RIR database for the space.323 of 636
Route object: RIR170.246.80.0/23Route object only in TC. Add it in the RIR database for the space.205 of 673
Route object: RIR177.67.156.0/23Route object only in TC. Add it in the RIR database for the space.205 of 673
Route object: RIR138.99.204.0/23Route object only in TC. Add it in the RIR database for the space.204 of 673
Route object: RIR138.99.206.0/23Route object only in TC. Add it in the RIR database for the space.204 of 673
Route object: RIR170.246.82.0/23Route object only in TC. Add it in the RIR database for the space.204 of 673
Route object: RIR177.67.158.0/23Route object only in TC. Add it in the RIR database for the space.204 of 673
Route object: RIR138.99.204.0/24Route object only in TC. Add it in the RIR database for the space.24 of 673
Route object: RIR138.99.205.0/24Route object only in TC. Add it in the RIR database for the space.24 of 673
Route object: RIR138.99.206.0/24Route object only in TC. Add it in the RIR database for the space.24 of 673
Route object: RIR138.99.207.0/24Route object only in TC. Add it in the RIR database for the space.24 of 673
Route object: RIR170.246.80.0/24Route object only in TC. Add it in the RIR database for the space.24 of 673
Route object: RIR170.246.81.0/24Route object only in TC. Add it in the RIR database for the space.24 of 673
Route object: RIR170.246.82.0/24Route object only in TC. Add it in the RIR database for the space.24 of 673
Route object: RIR170.246.83.0/24Route object only in TC. Add it in the RIR database for the space.24 of 673
Route object: RIR177.67.156.0/24Route object only in TC. Add it in the RIR database for the space.24 of 673
Route object: RIR177.67.157.0/24Route object only in TC. Add it in the RIR database for the space.24 of 673
Route object: RIR177.67.158.0/24Route object only in TC. Add it in the RIR database for the space.24 of 673
Route object: RIR177.67.159.0/24Route object only in TC. Add it in the RIR database for the space.24 of 673

Route objects not announced

Every route object with origin AS52686 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.