bgpreport

Network · data from 2026-11-12

AS197209 STN-EU-AS STN STORITVE d.o.o.

Registry name: STN-EU-AS STN STORITVE d.o.o., SI · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS197209, 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.
2a00:ee7::/48 Invalid: origin RIR databaseRIPE 65 10% 32
91.209.251.0/24 No ROA RIR databaseRIPE 673 100% 67
91.209.181.0/24 No ROA RIR databaseRIPE 671 100% 68
2001:67c:be0::/48 No ROA RIR databaseRIPE 636 100% 69

AS-SET

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

  • ROA: origin1
  • ROA: none3
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: origin2a00:ee7::/48ROAs covering it name AS5603, not AS197209. If AS197209 should announce it, add a ROA for AS197209.65 of 636
ROA: none91.209.251.0/24No ROA covers it. Add a ROA for AS197209, maxLength 24.673 of 673
ROA: none91.209.181.0/24No ROA covers it. Add a ROA for AS197209, maxLength 24.671 of 673
ROA: none2001:67c:be0::/48No ROA covers it. Add a ROA for AS197209, maxLength 48.636 of 636

Route objects not announced

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

83.122.16.0/20RIPEInvalid: origin
83.122.32.0/20RIPEInvalid: origin
83.122.48.0/20RIPEInvalid: origin
83.122.64.0/20RIPEInvalid: 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.