bgpreport

Network · data from 2026-11-12

AS267096 HELLO WEB TELECOMUNICACOES E SERVICOS

Registry name: AS267096 - HELLO WEB TELECOMUNICACOES E SERVICOS LTDA EPP, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS267096, 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.229.26.0/23 No ROA Nonecovered by 45.229.24.0/22 671 100% 66
2804:4814::/33 No ROA Nonecovered by 2804:4814::/32 344 54% 64
45.229.24.0/24 No ROA Nonecovered by 45.229.24.0/23 23 3%low visibility 10
45.229.25.0/24 No ROA Nonecovered by 45.229.24.0/23 23 3%low visibility 10
45.229.26.0/24 No ROA Nonecovered by 45.229.24.0/22 23 3%low visibility 10
45.229.27.0/24 No ROA Nonecovered by 45.229.24.0/22 23 3%low visibility 10
45.229.24.0/22 No ROA Other IRR onlyALTDB, RADB, TC 672 100% 66
45.229.24.0/23 No ROA Other IRR onlyALTDB 672 100% 66
2804:4814::/32 No ROA Other IRR onlyALTDB, RADB, TC 633 100% 67
2804:4814:8000::/33 No ROA Other IRR onlyALTDB 344 54% 64

AS-SET

PeeringDB's irr_as_set for AS267096: AS-267096. 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 (AS267096 isn't in the set, or no route object for AS267096 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 objectsAS267096 in itNot covered
AS-267096 ALTDB 4244 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 20 are in fix.csv.

  • ROA: none10
  • Route object: none6
  • Route object: RIR4
ChangePrefix or setDetailFull-table peers
ROA: none45.229.26.0/23No ROA covers it. Add a ROA for AS267096, maxLength 23.671 of 673
Route object: none45.229.26.0/23No route object for it. A route object for 45.229.24.0/22 with origin AS267096 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267096 in the RIR database for the space.671 of 673
ROA: none2804:4814::/33No ROA covers it. Add a ROA for AS267096, maxLength 33.344 of 636
Route object: none2804:4814::/33No route object for it. A route object for 2804:4814::/32 with origin AS267096 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267096 in the RIR database for the space.344 of 636
ROA: none45.229.24.0/24No ROA covers it. Add a ROA for AS267096, maxLength 24.23 of 673
Route object: none45.229.24.0/24No route object for it. A route object for 45.229.24.0/23 with origin AS267096 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267096 in the RIR database for the space.23 of 673
ROA: none45.229.25.0/24No ROA covers it. Add a ROA for AS267096, maxLength 24.23 of 673
Route object: none45.229.25.0/24No route object for it. A route object for 45.229.24.0/23 with origin AS267096 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267096 in the RIR database for the space.23 of 673
ROA: none45.229.26.0/24No ROA covers it. Add a ROA for AS267096, maxLength 24.23 of 673
Route object: none45.229.26.0/24No route object for it. A route object for 45.229.24.0/22 with origin AS267096 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267096 in the RIR database for the space.23 of 673
ROA: none45.229.27.0/24No ROA covers it. Add a ROA for AS267096, maxLength 24.23 of 673
Route object: none45.229.27.0/24No route object for it. A route object for 45.229.24.0/22 with origin AS267096 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267096 in the RIR database for the space.23 of 673
ROA: none45.229.24.0/22No ROA covers it. Add a ROA for AS267096, maxLength 22.672 of 673
Route object: RIR45.229.24.0/22Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.672 of 673
ROA: none45.229.24.0/23No ROA covers it. Add a ROA for AS267096, maxLength 23.672 of 673
Route object: RIR45.229.24.0/23Route object only in ALTDB. Add it in the RIR database for the space.672 of 673
ROA: none2804:4814::/32No ROA covers it. Add a ROA for AS267096, maxLength 32.633 of 636
Route object: RIR2804:4814::/32Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.633 of 636
ROA: none2804:4814:8000::/33No ROA covers it. Add a ROA for AS267096, maxLength 33.344 of 636
Route object: RIR2804:4814:8000::/33Route object only in ALTDB. Add it in the RIR database for the space.344 of 636

Route objects not announced

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