bgpreport

Network · data from 2026-11-12

AS263614 RVA TELECOM LTDA

Registry name: AS263614 - RVA TELECOM LTDA, BR · PeeringDB

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

Announced routes

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

168.232.220.0/23 Invalid: maxLength Nonecovered by 168.232.220.0/22 15 2%low visibility 7
168.232.222.0/23 Invalid: maxLength Nonecovered by 168.232.220.0/22 15 2%low visibility 7
177.23.108.0/23 Invalid: maxLength Nonecovered by 177.23.108.0/22 15 2%low visibility 7
177.23.110.0/23 Invalid: maxLength Nonecovered by 177.23.108.0/22 15 2%low visibility 7
2804:1004::/33 Valid Nonecovered by 2804:1004::/32 636 100% 67
2804:1004::/34 Valid Nonecovered by 2804:1004::/32 636 100% 67
2804:1004:4000::/34 Valid Nonecovered by 2804:1004::/32 636 100% 67
2804:1004:8000::/34 Valid Nonecovered by 2804:1004:8000::/33 636 100% 67
2804:1004:c000::/34 Valid Nonecovered by 2804:1004:8000::/33 636 100% 67
168.232.220.0/22 Valid Other IRR onlyALTDB 672 100% 67
177.23.108.0/22 Valid Other IRR onlyALTDB, RADB, TC 672 100% 67
168.232.220.0/24 Valid Other IRR onlyALTDB 671 100% 67
177.23.108.0/24 Valid Other IRR onlyALTDB, RADB 670 100% 67
168.232.222.0/24 Valid Other IRR onlyALTDB 666 99% 67
168.232.223.0/24 Valid Other IRR onlyALTDB 666 99% 67
177.23.109.0/24 Valid Other IRR onlyALTDB 666 99% 67
177.23.110.0/24 Valid Other IRR onlyALTDB 666 99% 67
177.23.111.0/24 Valid Other IRR onlyALTDB 666 99% 67
168.232.221.0/24 Valid Other IRR onlyALTDB 665 99% 67
2804:1004::/32 Valid Other IRR onlyALTDB, RADB, TC 636 100% 67
2804:1004:8000::/33 Valid Other IRR onlyRADB 636 100% 67

AS-SET

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

  • ROA: maxLength4
  • Route object: none9
  • Route object: RIR12
ChangePrefix or setDetailFull-table peers
ROA: maxLength168.232.220.0/23ROA 168.232.220.0/22 AS263614 has maxLength 22; the route is a /23. Raise the maxLength, or add a ROA for 168.232.220.0/23.15 of 673
Route object: none168.232.220.0/23No route object for it. A route object for 168.232.220.0/22 with origin AS263614 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263614 in the RIR database for the space.15 of 673
ROA: maxLength168.232.222.0/23ROA 168.232.220.0/22 AS263614 has maxLength 22; the route is a /23. Raise the maxLength, or add a ROA for 168.232.222.0/23.15 of 673
Route object: none168.232.222.0/23No route object for it. A route object for 168.232.220.0/22 with origin AS263614 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263614 in the RIR database for the space.15 of 673
ROA: maxLength177.23.108.0/23ROA 177.23.108.0/22 AS263614 has maxLength 22; the route is a /23. Raise the maxLength, or add a ROA for 177.23.108.0/23.15 of 673
Route object: none177.23.108.0/23No route object for it. A route object for 177.23.108.0/22 with origin AS263614 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263614 in the RIR database for the space.15 of 673
ROA: maxLength177.23.110.0/23ROA 177.23.108.0/22 AS263614 has maxLength 22; the route is a /23. Raise the maxLength, or add a ROA for 177.23.110.0/23.15 of 673
Route object: none177.23.110.0/23No route object for it. A route object for 177.23.108.0/22 with origin AS263614 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263614 in the RIR database for the space.15 of 673
Route object: none2804:1004::/33No route object for it. A route object for 2804:1004::/32 with origin AS263614 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263614 in the RIR database for the space.636 of 636
Route object: none2804:1004::/34No route object for it. A route object for 2804:1004::/32 with origin AS263614 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263614 in the RIR database for the space.636 of 636
Route object: none2804:1004:4000::/34No route object for it. A route object for 2804:1004::/32 with origin AS263614 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263614 in the RIR database for the space.636 of 636
Route object: none2804:1004:8000::/34No route object for it. A route object for 2804:1004:8000::/33 with origin AS263614 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263614 in the RIR database for the space.636 of 636
Route object: none2804:1004:c000::/34No route object for it. A route object for 2804:1004:8000::/33 with origin AS263614 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263614 in the RIR database for the space.636 of 636
Route object: RIR168.232.220.0/22Route object only in ALTDB. Add it in the RIR database for the space.672 of 673
Route object: RIR177.23.108.0/22Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR168.232.220.0/24Route object only in ALTDB. Add it in the RIR database for the space.671 of 673
Route object: RIR177.23.108.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR168.232.222.0/24Route object only in ALTDB. Add it in the RIR database for the space.666 of 673
Route object: RIR168.232.223.0/24Route object only in ALTDB. Add it in the RIR database for the space.666 of 673
Route object: RIR177.23.109.0/24Route object only in ALTDB. Add it in the RIR database for the space.666 of 673
Route object: RIR177.23.110.0/24Route object only in ALTDB. Add it in the RIR database for the space.666 of 673
Route object: RIR177.23.111.0/24Route object only in ALTDB. Add it in the RIR database for the space.666 of 673
Route object: RIR168.232.221.0/24Route object only in ALTDB. Add it in the RIR database for the space.665 of 673
Route object: RIR2804:1004::/32Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:1004:8000::/33Route object only in RADB. Add it in the RIR database for the space.636 of 636

Route objects not announced

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