bgpreport

Network · data from 2026-11-12

AS271385 FIBRA CHEGOU COMUNICACOES EIRELI

Registry name: AS271385 - FIBRA CHEGOU COMUNICACOES EIRELI, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS271385, 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.4.96.0/22 No ROA Other IRR onlyALTDB 671 100% 66
200.4.96.0/23 No ROA Other IRR onlyALTDB 671 100% 66
200.4.98.0/23 No ROA Other IRR onlyALTDB 671 100% 66
200.4.96.0/24 No ROA Other IRR onlyALTDB 670 100% 66
200.4.97.0/24 No ROA Other IRR onlyALTDB 670 100% 66
200.4.98.0/24 No ROA Other IRR onlyALTDB 670 100% 66
200.4.99.0/24 No ROA Other IRR onlyALTDB 670 100% 66
2804:7aac::/32 No ROA Other IRR onlyTC 633 100% 67

AS-SET

PeeringDB's irr_as_set for AS271385: AS271385:AS-FIBRACHEGOU. 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 (AS271385 isn't in the set, or no route object for AS271385 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 objectsAS271385 in itNot covered
AS271385:AS-FIBRACHEGOU ALTDB1 member set in no database: AS271385:AS-CUSTOMERS 219 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 17 are in fix.csv.

  • ROA: none8
  • Route object: RIR8
  • AS-SET: missing member1
ChangePrefix or setDetailFull-table peers
ROA: none200.4.96.0/22No ROA covers it. Add a ROA for AS271385, maxLength 22.671 of 673
Route object: RIR200.4.96.0/22Route object only in ALTDB. Add it in the RIR database for the space.671 of 673
ROA: none200.4.96.0/23No ROA covers it. Add a ROA for AS271385, maxLength 23.671 of 673
Route object: RIR200.4.96.0/23Route object only in ALTDB. Add it in the RIR database for the space.671 of 673
ROA: none200.4.98.0/23No ROA covers it. Add a ROA for AS271385, maxLength 23.671 of 673
Route object: RIR200.4.98.0/23Route object only in ALTDB. Add it in the RIR database for the space.671 of 673
ROA: none200.4.96.0/24No ROA covers it. Add a ROA for AS271385, maxLength 24.670 of 673
Route object: RIR200.4.96.0/24Route object only in ALTDB. Add it in the RIR database for the space.670 of 673
ROA: none200.4.97.0/24No ROA covers it. Add a ROA for AS271385, maxLength 24.670 of 673
Route object: RIR200.4.97.0/24Route object only in ALTDB. Add it in the RIR database for the space.670 of 673
ROA: none200.4.98.0/24No ROA covers it. Add a ROA for AS271385, maxLength 24.670 of 673
Route object: RIR200.4.98.0/24Route object only in ALTDB. Add it in the RIR database for the space.670 of 673
ROA: none200.4.99.0/24No ROA covers it. Add a ROA for AS271385, maxLength 24.670 of 673
Route object: RIR200.4.99.0/24Route object only in ALTDB. Add it in the RIR database for the space.670 of 673
ROA: none2804:7aac::/32No ROA covers it. Add a ROA for AS271385, maxLength 32.633 of 636
Route object: RIR2804:7aac::/32Route object only in TC. Add it in the RIR database for the space.633 of 636
AS-SET: missing memberAS271385:AS-FIBRACHEGOUAS271385:AS-FIBRACHEGOU (ALTDB) lists AS271385:AS-CUSTOMERS; no IRR database read has it.

Route objects not announced

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