bgpreport

Network · data from 2026-11-12

AS207192 Telcomdata

Registry name: OPTINETWORKS Anfeya LLC, KG · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS207192, 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.161.48.0/22 Valid RIR databaseRIPE 673 100% 66
185.161.51.0/24 Valid RIR databaseRIPE 672 100% 66
2a0f:5240::/32 Valid RIR databaseRIPE 636 100% 67
185.161.49.0/24 Valid RIR databaseRIPE 1 0%low visibility 1
185.161.50.0/24 Valid RIR databaseRIPE 1 0%low visibility 1

AS-SET

PeeringDB's irr_as_set for AS207192: RIPE::AS-TCDNET-PEERS. 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 (AS207192 isn't in the set, or no route object for AS207192 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 objectsAS207192 in itNot covered
RIPE::AS-TCDNET-PEERS RIPElists itself further down13 member sets in no database: AS-CMFTKZ, AS-DURABLE, AS-GLOBALNET02, AS-INITQ, AS-RACKCORP … 93411479,020 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 16 are in fix.csv.

  • AS-SET: missing member13
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
AS-SET: missing memberRIPE::AS-TCDNET-PEERSAS-TCDNET-PEERS (RIPE) lists AS-CMFTKZ; no IRR database read has it.
AS-SET: missing memberRIPE::AS-TCDNET-PEERSAS-TCDNET-PEERS (RIPE) lists AS-DURABLE; no IRR database read has it.
AS-SET: missing memberRIPE::AS-TCDNET-PEERSAS-TCDNET-PEERS (RIPE) lists AS-GLOBALNET02; no IRR database read has it.
AS-SET: missing memberRIPE::AS-TCDNET-PEERSAS-TCDNET-PEERS (RIPE) lists AS-INITQ; no IRR database read has it.
AS-SET: missing memberRIPE::AS-TCDNET-PEERSAS-TCDNET-PEERS (RIPE) lists AS-RACKCORP; no IRR database read has it.
AS-SET: missing memberRIPE::AS-TCDNET-PEERSAS-TCDNET-PEERS (RIPE) lists AS-SERVERSCOM; no IRR database read has it.
AS-SET: missing memberRIPE::AS-TCDNET-PEERSAS-TCDNET-PEERS (RIPE) lists AS-SET-55330; no IRR database read has it.
AS-SET: missing memberRIPE::AS-TCDNET-PEERSAS-TCDNET-PEERS (RIPE) lists AS-WZ-ASIA; no IRR database read has it.
AS-SET: missing memberRIPE::AS-TCDNET-PEERSAS-TCDNET-PEERS (RIPE) lists AS-WZ-EU; no IRR database read has it.
AS-SET: missing memberRIPE::AS-TCDNET-PEERSAS-TCDNET-PEERS (RIPE) lists AS131284:AS-ETA; no IRR database read has it.
AS-SET: missing memberRIPE::AS-TCDNET-PEERSAS-TCDNET-PEERS (RIPE) lists AS138322:AS-CUSTOMER; no IRR database read has it.
AS-SET: missing memberRIPE::AS-TCDNET-PEERSAS-TCDNET-PEERS (RIPE) lists AS14593:AS-SX-STARLINK; no IRR database read has it.
AS-SET: missing memberRIPE::AS-TCDNET-PEERSAS-TCDNET-PEERS (RIPE) lists AS207567:AS-INTEZIO; no IRR database read has it.

Route objects not announced

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

185.161.48.0/24RIPEValid
194.56.214.0/24RIPEValid
212.2.233.0/24RIPEValid

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.