bgpreport

Network · data from 2026-11-12

AS61657 JR NET INFORMATICA

Registry name: AS61657 - Jr Net Informatica Ltda - ME, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS61657, 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.

131.100.252.0/23 Valid Nonecovered by 131.100.252.0/22 669 99% 67
131.100.254.0/23 Valid Nonecovered by 131.100.252.0/22 669 99% 67
131.100.253.0/24 Valid Nonecovered by 131.100.252.0/22 666 99% 67
2804:1c80::/33 Valid Nonecovered by 2804:1c80::/32 355 56% 65
2804:1c80::/34 Valid Nonecovered by 2804:1c80::/32 355 56% 65
2804:1c80:4000::/34 Valid Nonecovered by 2804:1c80::/32 355 56% 65
2804:1c80:8000::/33 Valid Nonecovered by 2804:1c80::/32 355 56% 65
2804:1c80:8000::/34 Valid Nonecovered by 2804:1c80::/32 355 56% 65
2804:1c80:c000::/34 Valid Nonecovered by 2804:1c80::/32 355 56% 65
131.100.254.0/24 Valid Nonecovered by 131.100.252.0/22 215 32% 57
131.100.252.0/24 Valid Nonecovered by 131.100.252.0/22 2 0%low visibility 2
131.100.255.0/24 Valid Nonecovered by 131.100.252.0/22 2 0%low visibility 2
131.100.252.0/22 Valid Other IRR onlyRADB, TC 671 100% 67
2804:1c80::/32 Valid Other IRR onlyRADB, TC 632 99% 67

AS-SET

PeeringDB's irr_as_set for AS61657: AS61657. 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 (AS61657 isn't in the set, or no route object for AS61657 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 objectsAS61657 in itNot covered
AS61657 A single AS number, not a set: AS61657 (this network), 2 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 14 are in fix.csv.

  • Route object: none12
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
Route object: none131.100.252.0/23No route object for it. A route object for 131.100.252.0/22 with origin AS61657 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61657 in the RIR database for the space.669 of 673
Route object: none131.100.254.0/23No route object for it. A route object for 131.100.252.0/22 with origin AS61657 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61657 in the RIR database for the space.669 of 673
Route object: none131.100.253.0/24No route object for it. A route object for 131.100.252.0/22 with origin AS61657 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61657 in the RIR database for the space.666 of 673
Route object: none2804:1c80::/33No route object for it. A route object for 2804:1c80::/32 with origin AS61657 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61657 in the RIR database for the space.355 of 636
Route object: none2804:1c80::/34No route object for it. A route object for 2804:1c80::/32 with origin AS61657 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61657 in the RIR database for the space.355 of 636
Route object: none2804:1c80:4000::/34No route object for it. A route object for 2804:1c80::/32 with origin AS61657 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61657 in the RIR database for the space.355 of 636
Route object: none2804:1c80:8000::/33No route object for it. A route object for 2804:1c80::/32 with origin AS61657 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61657 in the RIR database for the space.355 of 636
Route object: none2804:1c80:8000::/34No route object for it. A route object for 2804:1c80::/32 with origin AS61657 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61657 in the RIR database for the space.355 of 636
Route object: none2804:1c80:c000::/34No route object for it. A route object for 2804:1c80::/32 with origin AS61657 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61657 in the RIR database for the space.355 of 636
Route object: none131.100.254.0/24No route object for it. A route object for 131.100.252.0/22 with origin AS61657 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61657 in the RIR database for the space.215 of 673
Route object: none131.100.252.0/24No route object for it. A route object for 131.100.252.0/22 with origin AS61657 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61657 in the RIR database for the space.2 of 673
Route object: none131.100.255.0/24No route object for it. A route object for 131.100.252.0/22 with origin AS61657 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61657 in the RIR database for the space.2 of 673
Route object: RIR131.100.252.0/22Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR2804:1c80::/32Route object only in RADB, TC. Add it in the RIR database for the space.632 of 636

Route objects not announced

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