bgpreport

Network · data from 2026-11-12

AS263496 Netpeu

Registry name: AS263496 - Netpeu Tecnologia e Internet Ltda, BR · PeeringDB

22IPv4 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
0Route objects not announced registered with origin AS263496, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS263496, 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.244.216.0/22 Valid Other IRR onlyRADB, TC 672 100% 66
191.243.56.0/21 Valid Other IRR onlyRADB, TC 672 100% 66
191.243.56.0/22 Valid Other IRR onlyTC 671 100% 66
191.243.56.0/23 Valid Other IRR onlyTC 671 100% 66
191.243.56.0/24 Valid Other IRR onlyTC 671 100% 66
191.243.57.0/24 Valid Other IRR onlyTC 671 100% 66
191.243.58.0/23 Valid Other IRR onlyTC 671 100% 66
191.243.58.0/24 Valid Other IRR onlyTC 671 100% 66
191.243.59.0/24 Valid Other IRR onlyTC 671 100% 66
191.243.60.0/22 Valid Other IRR onlyTC 671 100% 66
191.243.60.0/23 Valid Other IRR onlyTC 671 100% 66
191.243.60.0/24 Valid Other IRR onlyTC 671 100% 66
191.243.61.0/24 Valid Other IRR onlyTC 671 100% 66
191.243.62.0/23 Valid Other IRR onlyTC 671 100% 66
191.243.62.0/24 Valid Other IRR onlyRADB, TC 671 100% 66
191.243.63.0/24 Valid Other IRR onlyTC 671 100% 66
170.244.216.0/23 Valid Other IRR onlyTC 669 99% 67
170.244.216.0/24 Valid Other IRR onlyRADB, TC 669 99% 67
170.244.217.0/24 Valid Other IRR onlyRADB, TC 669 99% 67
170.244.218.0/23 Valid Other IRR onlyTC 669 99% 67
170.244.218.0/24 Valid Other IRR onlyRADB, TC 669 99% 67
170.244.219.0/24 Valid Other IRR onlyRADB, TC 669 99% 67
2804:12c0::/32 Valid Other IRR onlyRADB, TC 636 100% 67

AS-SET

PeeringDB's irr_as_set for AS263496: AS263496:AS-NETPEU. 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 (AS263496 isn't in the set, or no route object for AS263496 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 objectsAS263496 in itNot covered
AS263496:AS-NETPEU TC 1323 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 23 are in fix.csv.

  • Route object: RIR23
ChangePrefix or setDetailFull-table peers
Route object: RIR170.244.216.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR191.243.56.0/21Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR191.243.56.0/22Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR191.243.56.0/23Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR191.243.56.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR191.243.57.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR191.243.58.0/23Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR191.243.58.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR191.243.59.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR191.243.60.0/22Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR191.243.60.0/23Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR191.243.60.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR191.243.61.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR191.243.62.0/23Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR191.243.62.0/24Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR191.243.63.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR170.244.216.0/23Route object only in TC. Add it in the RIR database for the space.669 of 673
Route object: RIR170.244.216.0/24Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR170.244.217.0/24Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR170.244.218.0/23Route object only in TC. Add it in the RIR database for the space.669 of 673
Route object: RIR170.244.218.0/24Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR170.244.219.0/24Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR2804:12c0::/32Route object only in RADB, TC. Add it in the RIR database for the space.636 of 636

Route objects not announced

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