bgpreport

Network · data from 2026-11-12

AS262478 AUE Provedor de Internet

Registry name: AS262478 - AUE Provedor de Internet LTDA., BR · PeeringDB

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

Announced routes

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

177.47.244.0/23 Invalid: maxLength Nonecovered by 177.47.244.0/22 0 0%low visibility 1
177.47.250.0/23 Invalid: maxLength Nonecovered by 177.47.248.0/22 0 0%low visibility 1
177.47.249.0/24 Valid Nonecovered by 177.47.248.0/23 670 100% 67
177.47.240.0/20 Valid Other IRR onlyRADB, TC 672 100% 66
177.47.240.0/21 Valid Other IRR onlyRADB, TC 672 100% 66
177.47.248.0/21 Valid Other IRR onlyRADB, TC 672 100% 66
177.47.255.0/24 Valid Other IRR onlyRADB 671 100% 66
177.47.240.0/22 Valid Other IRR onlyTC 670 100% 67
177.47.244.0/22 Valid Other IRR onlyRADB, TC 670 100% 67
177.47.248.0/22 Valid Other IRR onlyTC 670 100% 67
177.47.252.0/22 Valid Other IRR onlyTC 670 100% 67
177.47.248.0/23 Valid Other IRR onlyTC 668 99% 67
2804:a78::/32 Valid Other IRR onlyRADB, TC 636 100% 67
2804:a78::/33 Valid Other IRR onlyRADB, TC 636 100% 67
177.47.240.0/23 Valid Other IRR onlyRADB, TC 207 31% 56
177.47.246.0/23 Valid Other IRR onlyTC 207 31% 56
177.47.252.0/23 Valid Other IRR onlyRADB, TC 207 31% 56
177.47.254.0/23 Valid Other IRR onlyTC 207 31% 56
177.47.242.0/23 Valid Other IRR onlyTC 206 31% 56

AS-SET

PeeringDB's irr_as_set for AS262478: TC::AS262478:AS-AUEPROVEDOR. 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 (AS262478 isn't in the set, or no route object for AS262478 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 objectsAS262478 in itNot covered
TC::AS262478:AS-AUEPROVEDOR TC 1116 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 21 are in fix.csv.

  • ROA: maxLength2
  • Route object: none3
  • Route object: RIR16
ChangePrefix or setDetailFull-table peers
ROA: maxLength177.47.244.0/23ROA 177.47.240.0/20 AS262478 has maxLength 20; ROA 177.47.240.0/21 AS262478 has maxLength 21; ROA 177.47.244.0/22 AS262478 has maxLength 22; the route is a /23. Raise the maxLength, or add a ROA for 177.47.244.0/23.0 of 673
Route object: none177.47.244.0/23No route object for it. A route object for 177.47.244.0/22 with origin AS262478 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262478 in the RIR database for the space.0 of 673
ROA: maxLength177.47.250.0/23ROA 177.47.240.0/20 AS262478 has maxLength 20; ROA 177.47.248.0/21 AS262478 has maxLength 21; ROA 177.47.248.0/22 AS262478 has maxLength 22; the route is a /23. Raise the maxLength, or add a ROA for 177.47.250.0/23.0 of 673
Route object: none177.47.250.0/23No route object for it. A route object for 177.47.248.0/22 with origin AS262478 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262478 in the RIR database for the space.0 of 673
Route object: none177.47.249.0/24No route object for it. A route object for 177.47.248.0/23 with origin AS262478 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262478 in the RIR database for the space.670 of 673
Route object: RIR177.47.240.0/20Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR177.47.240.0/21Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR177.47.248.0/21Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR177.47.255.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR177.47.240.0/22Route object only in TC. Add it in the RIR database for the space.670 of 673
Route object: RIR177.47.244.0/22Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR177.47.248.0/22Route object only in TC. Add it in the RIR database for the space.670 of 673
Route object: RIR177.47.252.0/22Route object only in TC. Add it in the RIR database for the space.670 of 673
Route object: RIR177.47.248.0/23Route object only in TC. Add it in the RIR database for the space.668 of 673
Route object: RIR2804:a78::/32Route object only in RADB, TC. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:a78::/33Route object only in RADB, TC. Add it in the RIR database for the space.636 of 636
Route object: RIR177.47.240.0/23Route object only in RADB, TC. Add it in the RIR database for the space.207 of 673
Route object: RIR177.47.246.0/23Route object only in TC. Add it in the RIR database for the space.207 of 673
Route object: RIR177.47.252.0/23Route object only in RADB, TC. Add it in the RIR database for the space.207 of 673
Route object: RIR177.47.254.0/23Route object only in TC. Add it in the RIR database for the space.207 of 673
Route object: RIR177.47.242.0/23Route object only in TC. Add it in the RIR database for the space.206 of 673

Route objects not announced

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