bgpreport

Network · data from 2026-11-12

AS267245 AS267245 - NETFACIL TELECOM

Registry name: AS267245 - NETFACIL TELECOM, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS267245, 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.
45.231.145.0/24 No ROA Nonecovered by 45.231.144.0/23 669 99% 66
45.231.144.0/24 No ROA Nonecovered by 45.231.144.0/23 668 99% 66
2804:4a84:8000::/33 No ROA Nonecovered by 2804:4a84::/32 630 99% 67
45.231.144.0/23 No ROA Other IRR onlyRADB 671 100% 66
2804:4a84::/32 No ROA Other IRR onlyRADB 630 99% 69

AS-SET

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

  • ROA: none5
  • Route object: none3
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
ROA: none45.231.145.0/24No ROA covers it. Add a ROA for AS267245, maxLength 24.669 of 673
Route object: none45.231.145.0/24No route object for it. A route object for 45.231.144.0/23 with origin AS267245 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267245 in the RIR database for the space.669 of 673
ROA: none45.231.144.0/24No ROA covers it. Add a ROA for AS267245, maxLength 24.668 of 673
Route object: none45.231.144.0/24No route object for it. A route object for 45.231.144.0/23 with origin AS267245 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267245 in the RIR database for the space.668 of 673
ROA: none2804:4a84:8000::/33No ROA covers it. Add a ROA for AS267245, maxLength 33.630 of 636
Route object: none2804:4a84:8000::/33No route object for it. A route object for 2804:4a84::/32 with origin AS267245 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267245 in the RIR database for the space.630 of 636
ROA: none45.231.144.0/23No ROA covers it. Add a ROA for AS267245, maxLength 23.671 of 673
Route object: RIR45.231.144.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none2804:4a84::/32No ROA covers it. Add a ROA for AS267245, maxLength 32.630 of 636
Route object: RIR2804:4a84::/32Route object only in RADB. Add it in the RIR database for the space.630 of 636

Route objects not announced

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