bgpreport

Network · data from 2026-11-12

AS204843 STERLY VERI MERKEZI YAZILIM VE SIBER GUVENLIK HIZMETLERI

Registry name: TR-STERLY_VERI_MERKEZI_YAZILIM_VE_SIBER_GUVENLIK_HIZMETLERI_ANONIM_SIRKETI STERLY VERI MERKEZI YAZILIM VE SIBER GUVENLIK HIZMETLERI A.S., TR · PeeringDB

1IPv4 routes 100.0% RPKI valid · 100.0% with a route object
15IPv6 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
0Low visibility seen by under 10% of full-table peers
3Route objects not announced registered with origin AS204843, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS204843, 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.254.54.0/24 Valid RIR databaseRIPE 673 100% 66
2a09:8b80::/29 Valid RIR databaseRIPE 634 100% 67
2a0a:bbc0::/29 Valid RIR databaseRIPE 634 100% 67
2a0e:6740::/29 Valid RIR databaseRIPE 634 100% 67
2a0e:8840::/29 Valid RIR databaseRIPE 634 100% 67
2a0e:c440::/29 Valid RIR databaseRIPE 634 100% 67
2a0f:c00::/29 Valid RIR databaseRIPE 634 100% 67
2a0f:72c0::/29 Valid RIR databaseRIPE 634 100% 67
2a0f:da80::/29 Valid RIR databaseRIPE 634 100% 67
2a11:1840::/29 Valid RIR databaseRIPE 632 99% 67
2a11:2d80::/29 Valid RIR databaseRIPE 632 99% 67
2a11:3f00::/29 Valid RIR databaseRIPE 632 99% 67
2a11:41c0::/29 Valid RIR databaseRIPE 632 99% 67
2a12:1a40::/29 Valid RIR databaseRIPE 632 99% 67
2a12:35c0::/29 Valid RIR databaseRIPE 632 99% 67
2a12:3cc0::/29 Valid RIR databaseRIPE 632 99% 67

AS-SET

PeeringDB's irr_as_set for AS204843: RS-STERLY-AS. 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 (AS204843 isn't in the set, or no route object for AS204843 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 objectsAS204843 in itNot covered
RS-STERLY-AS A route-set, not an AS-SET; route-sets aren't expanded.

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.

  • Route object: not announced3

Route objects not announced

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

154.16.3.0/24AFRINICInvalid: origin
154.16.22.0/24AFRINICInvalid: origin
154.16.47.0/24AFRINICInvalid: origin

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.