bgpreport

Network · data from 2026-11-12

AS200334 netops network

Registry name: netops-tr Alptekin Sunnetci, TR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS200334, 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.
44.31.49.0/24 No ROA Other IRR onlyRADB 672 100% 66
2a0c:f587:fffe::/48 Valid RIR databaseALTDB, RIPE 636 100% 69
2a0c:f587:ffff::/48 Valid RIR databaseALTDB, RIPE 636 100% 69
2602:feda:b8d::/48 Valid RIR databaseARIN 91 14% 43
2a0f:6580:104::/48 Valid RIR databaseRIPE 7 1%low visibility 4
2602:feda:b8c::/48 Valid RIR databaseARIN 3 0%low visibility 2

AS-SET

PeeringDB's irr_as_set for AS200334: RIPE::AS-OFIS-LINK. 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 (AS200334 isn't in the set, or no route object for AS200334 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 objectsAS200334 in itNot covered
RIPE::AS-OFIS-LINK RIPE 4159 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 3 are in fix.csv.

  • ROA: none1
  • Route object: RIR1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none44.31.49.0/24No ROA covers it. Add a ROA for AS200334, maxLength 24.672 of 673
Route object: RIR44.31.49.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

2a0e:b107:192::/48RIPENo 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.