AS61125 SABOTAGE SABOTAGE LLC
🇺🇸Org handle: ORG-SABO2-RIPE
RIPE NCCallocatedASPA Published
Announced Prefixes (BGP)
2total
1 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)256
Announced (BGP)256
IPv6 Addresses
Allocated (RIR)1.2×10²⁴
Announced (BGP)1.2×10²⁴
Routing hygiene
Score 10/100 · Low riskRPKI ROA coverage
100%
no RPKI invalid prefixes
IRR route objects
100%
no origin mismatches
Hijack signals
0
0 announced against others' ROAs, 0 own announced by others
Upstreams
1
diversity 0/100
- Only one upstream seen in the AS paths of its routes
Based on 2 announced prefixes, updated daily (2026-10-23). How the score works · RPKI explained
Listed on the threat map (2026-10-23)
Large hosting providers appear because attackers rent their servers, not necessarily because of the operator.
Announced Prefixes
(BGP)2|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | - | |
| Valid | RIPE | - |
Allocated Prefixes
(RIR)2Prefix | Country | RIR | Status |
|---|---|---|---|
| 45.66.35.0/24 | 🇸🇨 SC | RIPE | assigned |
| 2a09:61c0::/48 | 🇺🇸 US | RIPE | assigned |
All 2 announced prefixes of AS61125 →
Upstream Providers(1)
| ASN | Name |
|---|---|
| AS24875 | 🇳🇱NOVOSERVE-AS NovoServe B.V. |
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS61125 hands its own prefixes to: transit providers, or peers at an exchange.
- AS24875NOVOSERVE B.V2
Abuse Contact
External Links
Learn more
- What is an ASN?Autonomous systems, ASN ranges and how they are assigned
- RPKI and route origin validationWhat the RPKI badges on the prefix list mean
- How to run an ASPA checkVerify the upstream providers listed above
- IPv4 transfers in the RIPE NCC regionMonthly volume and the latest registry transfers
- ASN data in AI agents and SIEMMCP server and API integrations
API
Open https://api.ipctl.io/v1/asn/61125Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/61125" | jq