bgpreport

Network · data from 2026-11-12

AS267294 geracao real banda larga

Registry name: AS267294 - geracao real banda larga eireli, BR · PeeringDB

5IPv4 routes 0.0% RPKI valid · 40.0% with a route object
1IPv6 routes 0.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
6No 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 AS267294, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS267294, 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.233.49.0/24 No ROA Nonecovered by 45.233.48.0/22 207 31% 56
45.233.48.0/24 No ROA Nonecovered by 45.233.48.0/22 206 31% 56
45.233.51.0/24 No ROA Nonecovered by 45.233.48.0/22 206 31% 56
45.233.48.0/22 No ROA Other IRR onlyRADB, TC 668 99% 67
2804:4b44::/32 No ROA Other IRR onlyRADB, TC 631 99% 67
45.233.50.0/24 No ROA Other IRR onlyRADB 207 31% 56

AS-SET

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

  • ROA: none6
  • Route object: none3
  • Route object: RIR3
ChangePrefix or setDetailFull-table peers
ROA: none45.233.49.0/24No ROA covers it. Add a ROA for AS267294, maxLength 24.207 of 673
Route object: none45.233.49.0/24No route object for it. A route object for 45.233.48.0/22 with origin AS267294 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267294 in the RIR database for the space.207 of 673
ROA: none45.233.48.0/24No ROA covers it. Add a ROA for AS267294, maxLength 24.206 of 673
Route object: none45.233.48.0/24No route object for it. A route object for 45.233.48.0/22 with origin AS267294 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267294 in the RIR database for the space.206 of 673
ROA: none45.233.51.0/24No ROA covers it. Add a ROA for AS267294, maxLength 24.206 of 673
Route object: none45.233.51.0/24No route object for it. A route object for 45.233.48.0/22 with origin AS267294 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267294 in the RIR database for the space.206 of 673
ROA: none45.233.48.0/22No ROA covers it. Add a ROA for AS267294, maxLength 22.668 of 673
Route object: RIR45.233.48.0/22Route object only in RADB, TC. Add it in the RIR database for the space.668 of 673
ROA: none2804:4b44::/32No ROA covers it. Add a ROA for AS267294, maxLength 32.631 of 636
Route object: RIR2804:4b44::/32Route object only in RADB, TC. Add it in the RIR database for the space.631 of 636
ROA: none45.233.50.0/24No ROA covers it. Add a ROA for AS267294, maxLength 24.207 of 673
Route object: RIR45.233.50.0/24Route object only in RADB. Add it in the RIR database for the space.207 of 673

Route objects not announced

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