French autonomous system · RIPE NCC · Paris
AS215599
The autonomous system of Zkillu SAS from Paris
Zkillu SAS runs its own network. Own IPv4 and IPv6 address space, transit from two carriers, and physical presence in four facilities in Paris.
The network, live
Every announcement and withdrawal of our prefixes, as the RIPE BGP collectors receive them. The last few hours load with the page, then new messages arrive as they happen.
Connecting to the collectors…
— BGP messages in 48 h
- No message yet.
As seen from the global routing table
These figures come from RIPEstat and are read when the page loads. They describe what the global routing table sees.
3
Announced prefixes
—
Announcements covered by a valid ROA
2
Transit providers
Querying the routing table…
At a glance
- Organisation
- Zkillu SAS
- Registry
- RIPE NCC
- Network type
- Content
- Traffic
- 1–5 Gbps
- Ratio
- Balanced
- Scope
- Europe
- Country
- France
- IPv6
- Natively announced
- Peering
- Open, physical link required
Three ways in
The network
Four facilities in Paris, two transit providers, address space we own and sign with RPKI.
Architecture and addressingPeering
Open policy, no contract, no ratio requirement. IRR-based filtering and ROA validation.
Terms and requestTools
The live BGP feed, announced prefixes and their RPKI coverage, read from RIPE.
Watch the networkAn incident, an abuse report, a network emergency
The Zkillu NOC handles reports concerning AS215599 prefixes. Write to the abuse address and include timestamps, time zone and raw log excerpts.