bgpreport

Network · data from 2026-11-12

AS267564 FIBER TELECOM - TELECOMUNICAÇÃO DE DADOS

Registry name: AS267564 - FIBER TELECOM - TELECOMUNICACAO DE DADOS, 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
4Low visibility seen by under 10% of full-table peers
2Route objects not announced registered with origin AS267564, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS267564, 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.
201.182.212.0/22 No ROA Other IRR onlyNTTCOM, RADB, TC 671 100% 67
201.182.214.0/23 No ROA Other IRR onlyRADB, TC 671 100% 67
201.182.212.0/23 No ROA Other IRR onlyRADB, TC 669 99% 67
2804:4358::/32 No ROA Other IRR onlyNTTCOM, RADB, TC 361 57% 65
201.182.212.0/24 No ROA Other IRR onlyRADB, TC 2 0%low visibility 2
201.182.213.0/24 No ROA Other IRR onlyRADB, TC 2 0%low visibility 2
201.182.214.0/24 No ROA Other IRR onlyRADB, TC 2 0%low visibility 2
201.182.215.0/24 No ROA Other IRR onlyRADB, TC 2 0%low visibility 2

AS-SET

PeeringDB's irr_as_set for AS267564: TC::AS267564:AS-FIBERTELECOM. 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 (AS267564 isn't in the set, or no route object for AS267564 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 objectsAS267564 in itNot covered
TC::AS267564:AS-FIBERTELECOM TC 43553 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 18 are in fix.csv.

  • ROA: none8
  • Route object: RIR8
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none201.182.212.0/22No ROA covers it. Add a ROA for AS267564, maxLength 22.671 of 673
Route object: RIR201.182.212.0/22Route object only in NTTCOM, RADB, TC. Add it in the RIR database for the space.671 of 673
ROA: none201.182.214.0/23No ROA covers it. Add a ROA for AS267564, maxLength 23.671 of 673
Route object: RIR201.182.214.0/23Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
ROA: none201.182.212.0/23No ROA covers it. Add a ROA for AS267564, maxLength 23.669 of 673
Route object: RIR201.182.212.0/23Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
ROA: none2804:4358::/32No ROA covers it. Add a ROA for AS267564, maxLength 32.361 of 636
Route object: RIR2804:4358::/32Route object only in NTTCOM, RADB, TC. Add it in the RIR database for the space.361 of 636
ROA: none201.182.212.0/24No ROA covers it. Add a ROA for AS267564, maxLength 24.2 of 673
Route object: RIR201.182.212.0/24Route object only in RADB, TC. Add it in the RIR database for the space.2 of 673
ROA: none201.182.213.0/24No ROA covers it. Add a ROA for AS267564, maxLength 24.2 of 673
Route object: RIR201.182.213.0/24Route object only in RADB, TC. Add it in the RIR database for the space.2 of 673
ROA: none201.182.214.0/24No ROA covers it. Add a ROA for AS267564, maxLength 24.2 of 673
Route object: RIR201.182.214.0/24Route object only in RADB, TC. Add it in the RIR database for the space.2 of 673
ROA: none201.182.215.0/24No ROA covers it. Add a ROA for AS267564, maxLength 24.2 of 673
Route object: RIR201.182.215.0/24Route object only in RADB, TC. Add it in the RIR database for the space.2 of 673

Route objects not announced

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

2804:4358::/33TCNo ROA
2804:4358:8000::/33TCNo 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.