bgpreport

Network · data from 2026-11-12

AS269243 RedeVista Telecom

Registry name: AS269243 - REDEVISTA TELECOMUNICACOES LTDA, BR · PeeringDB

6IPv4 routes 0.0% RPKI valid · 33.3% with a route object
3IPv6 routes 0.0% RPKI valid · 33.3% with a route object
0RPKI invalid 0 origin · 0 maxLength
9No ROA 6 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS269243, seen from no peer

Announced routes

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

200.196.44.0/23 No ROA Nonecovered by 200.196.44.0/22 672 100% 66
200.196.46.0/23 No ROA Nonecovered by 200.196.44.0/22 672 100% 66
45.182.240.0/23 No ROA Nonecovered by 45.182.240.0/22 671 100% 66
45.182.242.0/23 No ROA Nonecovered by 45.182.240.0/22 670 100% 66
2804:6194::/33 No ROA Nonecovered by 2804:6194::/32 634 100% 67
2804:6194:8000::/33 No ROA Nonecovered by 2804:6194::/32 634 100% 67
45.182.240.0/22 No ROA Other IRR onlyRADB, TC 672 100% 66
200.196.44.0/22 No ROA Other IRR onlyRADB 672 100% 66
2804:6194::/32 No ROA Other IRR onlyRADB, TC 633 100% 67

AS-SET

PeeringDB's irr_as_set for AS269243: AS-269243. 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 (AS269243 isn't in the set, or no route object for AS269243 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 objectsAS269243 in itNot covered
AS-269243 In no IRR database read today.

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 19 are in fix.csv.

  • ROA: none9
  • Route object: none6
  • Route object: RIR3
  • AS-SET: not found1
ChangePrefix or setDetailFull-table peers
ROA: none200.196.44.0/23No ROA covers it. Add a ROA for AS269243, maxLength 23.672 of 673
Route object: none200.196.44.0/23No route object for it. A route object for 200.196.44.0/22 with origin AS269243 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269243 in the RIR database for the space.672 of 673
ROA: none200.196.46.0/23No ROA covers it. Add a ROA for AS269243, maxLength 23.672 of 673
Route object: none200.196.46.0/23No route object for it. A route object for 200.196.44.0/22 with origin AS269243 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269243 in the RIR database for the space.672 of 673
ROA: none45.182.240.0/23No ROA covers it. Add a ROA for AS269243, maxLength 23.671 of 673
Route object: none45.182.240.0/23No route object for it. A route object for 45.182.240.0/22 with origin AS269243 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269243 in the RIR database for the space.671 of 673
ROA: none45.182.242.0/23No ROA covers it. Add a ROA for AS269243, maxLength 23.670 of 673
Route object: none45.182.242.0/23No route object for it. A route object for 45.182.240.0/22 with origin AS269243 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269243 in the RIR database for the space.670 of 673
ROA: none2804:6194::/33No ROA covers it. Add a ROA for AS269243, maxLength 33.634 of 636
Route object: none2804:6194::/33No route object for it. A route object for 2804:6194::/32 with origin AS269243 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269243 in the RIR database for the space.634 of 636
ROA: none2804:6194:8000::/33No ROA covers it. Add a ROA for AS269243, maxLength 33.634 of 636
Route object: none2804:6194:8000::/33No route object for it. A route object for 2804:6194::/32 with origin AS269243 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269243 in the RIR database for the space.634 of 636
ROA: none45.182.240.0/22No ROA covers it. Add a ROA for AS269243, maxLength 22.672 of 673
Route object: RIR45.182.240.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
ROA: none200.196.44.0/22No ROA covers it. Add a ROA for AS269243, maxLength 22.672 of 673
Route object: RIR200.196.44.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none2804:6194::/32No ROA covers it. Add a ROA for AS269243, maxLength 32.633 of 636
Route object: RIR2804:6194::/32Route object only in RADB, TC. Add it in the RIR database for the space.633 of 636
AS-SET: not foundAS-269243PeeringDB names AS-269243; no IRR database read has it.

Route objects not announced

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