bgpreport

Network · data from 2026-11-12

AS208260 STOEGE Daniel Stocker

Registry name: STOEGE Daniel Stocker, CH · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS208260, 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.
2a0e:97c0:740::/48 No ROA Nonecovered by 2a0e:97c0:740::/44 636 100% 68
2a0e:97c0:741::/48 No ROA Nonecovered by 2a0e:97c0:740::/44 636 100% 68
2a0e:97c0:743::/48 No ROA Nonecovered by 2a0e:97c0:740::/44 636 100% 68
2a0e:97c0:742::/48 No ROA Nonecovered by 2a0e:97c0:740::/44 1 0%low visibility 1

AS-SET

AS208260 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 9 are in fix.csv.

  • ROA: none4
  • Route object: none4
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none2a0e:97c0:740::/48No ROA covers it. Add a ROA for AS208260, maxLength 48.636 of 636
Route object: none2a0e:97c0:740::/48No route object for it. A route object for 2a0e:97c0:740::/44 with origin AS208260 covers it (filters allowing more-specifics accept it). Add a route object with origin AS208260 in the RIR database for the space.636 of 636
ROA: none2a0e:97c0:741::/48No ROA covers it. Add a ROA for AS208260, maxLength 48.636 of 636
Route object: none2a0e:97c0:741::/48No route object for it. A route object for 2a0e:97c0:740::/44 with origin AS208260 covers it (filters allowing more-specifics accept it). Add a route object with origin AS208260 in the RIR database for the space.636 of 636
ROA: none2a0e:97c0:743::/48No ROA covers it. Add a ROA for AS208260, maxLength 48.636 of 636
Route object: none2a0e:97c0:743::/48No route object for it. A route object for 2a0e:97c0:740::/44 with origin AS208260 covers it (filters allowing more-specifics accept it). Add a route object with origin AS208260 in the RIR database for the space.636 of 636
ROA: none2a0e:97c0:742::/48No ROA covers it. Add a ROA for AS208260, maxLength 48.1 of 636
Route object: none2a0e:97c0:742::/48No route object for it. A route object for 2a0e:97c0:740::/44 with origin AS208260 covers it (filters allowing more-specifics accept it). Add a route object with origin AS208260 in the RIR database for the space.1 of 636

Route objects not announced

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

2a0e:97c0:740::/44RADBNo 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.