bgpreport

Network · data from 2026-11-12

AS60757 Optinet

Registry name: OPTINET-AS Optinet LLP, KZ · PeeringDB

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

Announced routes

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

185.217.188.0/23 No ROA None 670 100% 67
85.92.120.0/23 No ROA RIR databaseRIPE 673 100% 67
130.193.6.0/24 No ROA RIR databaseRIPE 673 100% 67
45.132.84.0/24 Valid RIR databaseRIPE 673 100% 67
45.143.89.0/24 Valid RIR databaseRIPE 673 100% 67
45.143.91.0/24 Valid RIR databaseRIPE 673 100% 67
85.92.120.0/24 Valid RIR databaseRIPE 673 100% 67
85.92.121.0/24 Valid RIR databaseRIPE 673 100% 67
85.92.122.0/24 Valid RIR databaseRIPE 673 100% 67
85.92.123.0/24 Valid RIR databaseRIPE 673 100% 67
185.217.188.0/24 Valid RIR databaseRIPE 673 100% 67
185.217.190.0/23 Valid RIR databaseRIPE 673 100% 67
2a0d:bcc0::/32 Valid RIR databaseRIPE 636 100% 68
2a0d:bcc1::/32 Valid RIR databaseRIPE 636 100% 68
2a0d:bcc2::/32 Valid RIR databaseRIPE 636 100% 68
185.217.190.0/24 Valid RIR databaseRIPE 1 0%low visibility 1
185.217.191.0/24 Valid RIR databaseRIPE 1 0%low visibility 1
185.217.189.0/24 Valid RIR databaseRIPE 0 0%low visibility 1

AS-SET

PeeringDB's irr_as_set for AS60757: RIPE::AS-SET-OPTINET. 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 (AS60757 isn't in the set, or no route object for AS60757 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 objectsAS60757 in itNot covered
RIPE::AS-SET-OPTINET RIPElists itself further down8 member sets in no database: AS-CMFTKZ, AS-DURABLE, AS-GLOBALNET02, AS-INITQ, AS-SERVERSCOM … 6677930,291 Yes 1

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: none3
  • Route object: none1
  • AS-SET: missing member8
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none185.217.188.0/23No ROA covers it. Add a ROA for AS60757, maxLength 23.670 of 673
Route object: none185.217.188.0/23No route object for it. Add a route object with origin AS60757 in the RIR database for the space.670 of 673
ROA: none85.92.120.0/23No ROA covers it. Add a ROA for AS60757, maxLength 23.673 of 673
ROA: none130.193.6.0/24No ROA covers it. Add a ROA for AS60757, maxLength 24.673 of 673
AS-SET: missing memberRIPE::AS-SET-OPTINETAS-SET-OPTINET (RIPE) lists AS-CMFTKZ; no IRR database read has it.
AS-SET: missing memberRIPE::AS-SET-OPTINETAS-SET-OPTINET (RIPE) lists AS-DURABLE; no IRR database read has it.
AS-SET: missing memberRIPE::AS-SET-OPTINETAS-SET-OPTINET (RIPE) lists AS-GLOBALNET02; no IRR database read has it.
AS-SET: missing memberRIPE::AS-SET-OPTINETAS-SET-OPTINET (RIPE) lists AS-INITQ; no IRR database read has it.
AS-SET: missing memberRIPE::AS-SET-OPTINETAS-SET-OPTINET (RIPE) lists AS-SERVERSCOM; no IRR database read has it.
AS-SET: missing memberRIPE::AS-SET-OPTINETAS-SET-OPTINET (RIPE) lists AS-WZ-ASIA; no IRR database read has it.
AS-SET: missing memberRIPE::AS-SET-OPTINETAS-SET-OPTINET (RIPE) lists AS-WZ-EU; no IRR database read has it.
AS-SET: missing memberRIPE::AS-SET-OPTINETAS-SET-OPTINET (RIPE) lists AS207567:AS-INTEZIO; no IRR database read has it.

Route objects not announced

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

45.143.90.0/24RIPENo ROA
176.96.249.0/24RIPENo ROA
2a0d:bcc0::/29RIPENo ROA
2a0d:bcc0:1::/48RIPEValid
2a0d:bcc0:2::/48RIPEValid
2a0d:bcc0:3::/48RIPEValid

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.