bgpreport

Network · data from 2026-11-12

AS267519 AS267519 - CONEXAO INFORMATICA SILVA LTDA

Registry name: AS267519 - CONEXAO INFORMATICA SILVA LTDA, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS267519, 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.
201.182.152.0/23 No ROA Nonecovered by 201.182.152.0/22 667 99% 67
201.182.152.0/24 No ROA Nonecovered by 201.182.152.0/22 667 99% 67
201.182.153.0/24 No ROA Nonecovered by 201.182.152.0/22 667 99% 67
201.182.154.0/23 No ROA Nonecovered by 201.182.152.0/22 667 99% 67
201.182.154.0/24 No ROA Nonecovered by 201.182.152.0/22 667 99% 67
201.182.155.0/24 No ROA Nonecovered by 201.182.152.0/22 667 99% 67
2804:42b0::/33 No ROA Nonecovered by 2804:42b0::/32 631 99% 67
2804:42b0:8000::/33 No ROA Nonecovered by 2804:42b0::/32 631 99% 67
201.182.152.0/22 No ROA Other IRR onlyALTDB, RADB 666 99% 67
2804:42b0::/32 No ROA Other IRR onlyALTDB, RADB 631 99% 67

AS-SET

AS267519 isn't in PeeringDB, where networks name their AS-SET.

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: none10
  • Route object: none8
  • Route object: RIR2
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none201.182.152.0/23No ROA covers it. Add a ROA for AS267519, maxLength 23.667 of 673
Route object: none201.182.152.0/23No route object for it. A route object for 201.182.152.0/22 with origin AS267519 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267519 in the RIR database for the space.667 of 673
ROA: none201.182.152.0/24No ROA covers it. Add a ROA for AS267519, maxLength 24.667 of 673
Route object: none201.182.152.0/24No route object for it. A route object for 201.182.152.0/22 with origin AS267519 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267519 in the RIR database for the space.667 of 673
ROA: none201.182.153.0/24No ROA covers it. Add a ROA for AS267519, maxLength 24.667 of 673
Route object: none201.182.153.0/24No route object for it. A route object for 201.182.152.0/22 with origin AS267519 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267519 in the RIR database for the space.667 of 673
ROA: none201.182.154.0/23No ROA covers it. Add a ROA for AS267519, maxLength 23.667 of 673
Route object: none201.182.154.0/23No route object for it. A route object for 201.182.152.0/22 with origin AS267519 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267519 in the RIR database for the space.667 of 673
ROA: none201.182.154.0/24No ROA covers it. Add a ROA for AS267519, maxLength 24.667 of 673
Route object: none201.182.154.0/24No route object for it. A route object for 201.182.152.0/22 with origin AS267519 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267519 in the RIR database for the space.667 of 673
ROA: none201.182.155.0/24No ROA covers it. Add a ROA for AS267519, maxLength 24.667 of 673
Route object: none201.182.155.0/24No route object for it. A route object for 201.182.152.0/22 with origin AS267519 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267519 in the RIR database for the space.667 of 673
ROA: none2804:42b0::/33No ROA covers it. Add a ROA for AS267519, maxLength 33.631 of 636
Route object: none2804:42b0::/33No route object for it. A route object for 2804:42b0::/32 with origin AS267519 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267519 in the RIR database for the space.631 of 636
ROA: none2804:42b0:8000::/33No ROA covers it. Add a ROA for AS267519, maxLength 33.631 of 636
Route object: none2804:42b0:8000::/33No route object for it. A route object for 2804:42b0::/32 with origin AS267519 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267519 in the RIR database for the space.631 of 636
ROA: none201.182.152.0/22No ROA covers it. Add a ROA for AS267519, maxLength 22.666 of 673
Route object: RIR201.182.152.0/22Route object only in ALTDB, RADB. Add it in the RIR database for the space.666 of 673
ROA: none2804:42b0::/32No ROA covers it. Add a ROA for AS267519, maxLength 32.631 of 636
Route object: RIR2804:42b0::/32Route object only in ALTDB, RADB. Add it in the RIR database for the space.631 of 636

Route objects not announced

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

164.163.100.0/22RADBNo 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.