bgpreport

Network · data from 2026-11-12

AS267455 FIBRACOM TELECOMUNICACOES E SERVICOS EIRELI - ME

Registry name: AS267455 - FIBRACOM TELECOMUNICACOES E SERVICOS EIRELI - ME, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS267455, 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.

164.163.220.0/23 No ROA Other IRR onlyTC 672 100% 67
164.163.220.0/24 No ROA Other IRR onlyRADB, TC 672 100% 67
164.163.223.0/24 No ROA Other IRR onlyRADB, TC 672 100% 66
164.163.221.0/24 No ROA Other IRR onlyRADB, TC 671 100% 67
164.163.222.0/24 No ROA Other IRR onlyRADB, TC 666 99% 67
2804:41c4:c000::/34 No ROA Other IRR onlyTC 635 100% 69
2804:41c4::/34 No ROA Other IRR onlyTC 633 100% 67
2804:41c4:4000::/34 No ROA Other IRR onlyTC 633 100% 67
2804:41c4:8000::/34 No ROA Other IRR onlyTC 633 100% 67

AS-SET

PeeringDB's irr_as_set for AS267455: AS267455:AS-SET. 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 (AS267455 isn't in the set, or no route object for AS267455 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 objectsAS267455 in itNot covered
AS267455:AS-SET In no IRR database read today.

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

  • ROA: none9
  • Route object: RIR9
  • AS-SET: not found1
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none164.163.220.0/23No ROA covers it. Add a ROA for AS267455, maxLength 23.672 of 673
Route object: RIR164.163.220.0/23Route object only in TC. Add it in the RIR database for the space.672 of 673
ROA: none164.163.220.0/24No ROA covers it. Add a ROA for AS267455, maxLength 24.672 of 673
Route object: RIR164.163.220.0/24Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
ROA: none164.163.223.0/24No ROA covers it. Add a ROA for AS267455, maxLength 24.672 of 673
Route object: RIR164.163.223.0/24Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
ROA: none164.163.221.0/24No ROA covers it. Add a ROA for AS267455, maxLength 24.671 of 673
Route object: RIR164.163.221.0/24Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
ROA: none164.163.222.0/24No ROA covers it. Add a ROA for AS267455, maxLength 24.666 of 673
Route object: RIR164.163.222.0/24Route object only in RADB, TC. Add it in the RIR database for the space.666 of 673
ROA: none2804:41c4:c000::/34No ROA covers it. Add a ROA for AS267455, maxLength 34.635 of 636
Route object: RIR2804:41c4:c000::/34Route object only in TC. Add it in the RIR database for the space.635 of 636
ROA: none2804:41c4::/34No ROA covers it. Add a ROA for AS267455, maxLength 34.633 of 636
Route object: RIR2804:41c4::/34Route object only in TC. Add it in the RIR database for the space.633 of 636
ROA: none2804:41c4:4000::/34No ROA covers it. Add a ROA for AS267455, maxLength 34.633 of 636
Route object: RIR2804:41c4:4000::/34Route object only in TC. Add it in the RIR database for the space.633 of 636
ROA: none2804:41c4:8000::/34No ROA covers it. Add a ROA for AS267455, maxLength 34.633 of 636
Route object: RIR2804:41c4:8000::/34Route object only in TC. Add it in the RIR database for the space.633 of 636
AS-SET: not foundAS267455:AS-SETPeeringDB names AS267455:AS-SET; no IRR database read has it.

Route objects not announced

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

164.163.220.0/22RADB, TCNo ROA
164.163.222.0/23RADB, TCNo ROA
200.229.240.0/22RADBNo ROA
2804:41c4::/32RADB, TCNo ROA
2804:41c4::/36RADBNo ROA
2804:78c8::/32RADBNo 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.