bgpreport

Network · data from 2026-11-12

AS267354 FOREST TELECOM TECNOLOGIA EM COMUNICACOES EIRELI

Registry name: AS267354 - FOREST TELECOM, BR · PeeringDB

1IPv4 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
2No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
4Route objects not announced registered with origin AS267354, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS267354, 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.80.0/23 No ROA Other IRR onlyALTDB, RADB 663 99% 67
2804:4c2c::/32 No ROA Other IRR onlyRADB 631 99% 67

AS-SET

PeeringDB's irr_as_set for AS267354: AS-FOREST. 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 (AS267354 isn't in the set, or no route object for AS267354 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 objectsAS267354 in itNot covered
AS-FOREST 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 9 are in fix.csv.

  • ROA: none2
  • Route object: RIR2
  • AS-SET: not found1
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none45.233.80.0/23No ROA covers it. Add a ROA for AS267354, maxLength 23.663 of 673
Route object: RIR45.233.80.0/23Route object only in ALTDB, RADB. Add it in the RIR database for the space.663 of 673
ROA: none2804:4c2c::/32No ROA covers it. Add a ROA for AS267354, maxLength 32.631 of 636
Route object: RIR2804:4c2c::/32Route object only in RADB. Add it in the RIR database for the space.631 of 636
AS-SET: not foundAS-FORESTPeeringDB names AS-FOREST; no IRR database read has it.

Route objects not announced

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

45.233.80.0/24ALTDBNo ROA
45.233.81.0/24ALTDBNo ROA
2804:4c2c::/33RADBNo ROA
2804:4c2c:8000::/33RADBNo 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.