bgpreport

Network · data from 2026-11-12

AS61651 NAZANET

Registry name: AS61651 - PAULO JUNIOR DO NASCIMENTO, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS61651, 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.168.0/23 No ROA Nonecovered by 131.100.168.0/22 671 100% 67
131.100.20.0/22 No ROA Other IRR onlyRADB, TC 672 100% 67
131.100.168.0/24 No ROA Other IRR onlyTC 672 100% 67
131.100.170.0/24 No ROA Other IRR onlyTC 672 100% 67
170.150.108.0/23 No ROA Other IRR onlyTC 672 100% 67
177.39.100.0/22 No ROA Other IRR onlyRADB, TC 672 100% 67
131.100.171.0/24 No ROA Other IRR onlyRADB, TC 671 100% 67
170.150.110.0/23 No ROA Other IRR onlyTC 670 100% 67
177.39.102.0/24 No ROA Other IRR onlyTC 669 99% 66
2804:1bac:8000::/33 No ROA Other IRR onlyTC 635 100% 70
2804:1bac::/33 No ROA Other IRR onlyTC 626 98% 67

AS-SET

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

  • ROA: none11
  • Route object: none1
  • Route object: RIR10
  • Route object: not announced18
ChangePrefix or setDetailFull-table peers
ROA: none131.100.168.0/23No ROA covers it. Add a ROA for AS61651, maxLength 23.671 of 673
Route object: none131.100.168.0/23No route object for it. A route object for 131.100.168.0/22 with origin AS61651 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61651 in the RIR database for the space.671 of 673
ROA: none131.100.20.0/22No ROA covers it. Add a ROA for AS61651, maxLength 22.672 of 673
Route object: RIR131.100.20.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
ROA: none131.100.168.0/24No ROA covers it. Add a ROA for AS61651, maxLength 24.672 of 673
Route object: RIR131.100.168.0/24Route object only in TC. Add it in the RIR database for the space.672 of 673
ROA: none131.100.170.0/24No ROA covers it. Add a ROA for AS61651, maxLength 24.672 of 673
Route object: RIR131.100.170.0/24Route object only in TC. Add it in the RIR database for the space.672 of 673
ROA: none170.150.108.0/23No ROA covers it. Add a ROA for AS61651, maxLength 23.672 of 673
Route object: RIR170.150.108.0/23Route object only in TC. Add it in the RIR database for the space.672 of 673
ROA: none177.39.100.0/22No ROA covers it. Add a ROA for AS61651, maxLength 22.672 of 673
Route object: RIR177.39.100.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
ROA: none131.100.171.0/24No ROA covers it. Add a ROA for AS61651, maxLength 24.671 of 673
Route object: RIR131.100.171.0/24Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
ROA: none170.150.110.0/23No ROA covers it. Add a ROA for AS61651, maxLength 23.670 of 673
Route object: RIR170.150.110.0/23Route object only in TC. Add it in the RIR database for the space.670 of 673
ROA: none177.39.102.0/24No ROA covers it. Add a ROA for AS61651, maxLength 24.669 of 673
Route object: RIR177.39.102.0/24Route object only in TC. Add it in the RIR database for the space.669 of 673
ROA: none2804:1bac:8000::/33No ROA covers it. Add a ROA for AS61651, maxLength 33.635 of 636
Route object: RIR2804:1bac:8000::/33Route object only in TC. Add it in the RIR database for the space.635 of 636
ROA: none2804:1bac::/33No ROA covers it. Add a ROA for AS61651, maxLength 33.626 of 636
Route object: RIR2804:1bac::/33Route object only in TC. Add it in the RIR database for the space.626 of 636

Route objects not announced

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

131.100.20.0/23TCNo ROA
131.100.20.0/24TCNo ROA
131.100.21.0/24TCNo ROA
131.100.22.0/23TCNo ROA
131.100.22.0/24TCNo ROA
131.100.23.0/24TCNo ROA
131.100.168.0/22RADB, TCNo ROA
131.100.169.0/24TCNo ROA
170.150.108.0/22RADB, TCNo ROA
170.150.108.0/24TCNo ROA
170.150.109.0/24TCNo ROA
170.150.110.0/24TCNo ROA
170.150.111.0/24TCNo ROA
177.39.100.0/23TCNo ROA
177.39.100.0/24TCNo ROA
177.39.102.0/23TCNo ROA
2804:1bac::/32RADB, TCNo ROA
2804:1c58::/32RADBNo 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.