bgpreport

Network · data from 2026-11-12

AS270977 AS270977 - OPTIMUS NETWORK EIRELI - ME

Registry name: AS270977 - OPTIMUS NETWORK EIRELI - ME, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS270977, 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.
177.74.96.0/24 No ROA Nonecovered by 177.74.96.0/22 667 99% 67
177.74.98.0/23 No ROA Nonecovered by 177.74.96.0/22 666 99% 67
2804:7460::/32 No ROA Other IRR onlyALTDB, NTTCOM, RADB 634 100% 67

AS-SET

AS270977 isn't in PeeringDB, where networks name their AS-SET.

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

  • ROA: none3
  • Route object: none2
  • Route object: RIR1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none177.74.96.0/24No ROA covers it. Add a ROA for AS270977, maxLength 24.667 of 673
Route object: none177.74.96.0/24No route object for it. A route object for 177.74.96.0/22 with origin AS270977 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270977 in the RIR database for the space.667 of 673
ROA: none177.74.98.0/23No ROA covers it. Add a ROA for AS270977, maxLength 23.666 of 673
Route object: none177.74.98.0/23No route object for it. A route object for 177.74.96.0/22 with origin AS270977 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270977 in the RIR database for the space.666 of 673
ROA: none2804:7460::/32No ROA covers it. Add a ROA for AS270977, maxLength 32.634 of 636
Route object: RIR2804:7460::/32Route object only in ALTDB, NTTCOM, RADB. Add it in the RIR database for the space.634 of 636

Route objects not announced

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

177.74.96.0/22ALTDB, NTTCOM, RADBNo 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.