AS28878 SIGNET-AS Signet B.V.
🇳🇱Org handle: ORG-SI6-RIPE
Signet B.V.
RIPE NCCallocated
Announced Prefixes (BGP)
124total
20 IPv4104 IPv6
IPv4 Addresses
Allocated (RIR)56,576
Announced (BGP)57,856
IPv6 Addresses
Allocated (RIR)6.3×10²⁹
Announced (BGP)6.3×10²⁹
Prefix Limit (IPv4)
100
Prefix Limit (IPv6)
500
Country
🇳🇱 NLRIR
RIPE NCCStatus
allocated
Allocated
2003-03-25
Routing hygiene
Score 11/100 · Low riskRPKI ROA coverage
96.8%
no RPKI invalid prefixes
IRR route objects
96%
5 prefixes registered for another origin
Hijack signals
0
0 announced against others' ROAs, 0 own announced by others
Upstreams
2
diversity 8/100
- Routes concentrated on one upstream (96% of routes)
Based on 124 announced prefixes, updated daily (2026-10-24). How the score works · RPKI explained
Announced Prefixes
(BGP)124|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | - | |
| Valid | RIPE | - | |
| Valid | RIPE | - | |
| Valid | RIPE | - | |
| Valid | RIPE | - | |
| Valid | RIPE | - | |
| Valid | RIPE | - | |
| Valid | RIPE | - | |
85.10.171.0/24MOAS | Valid | - | - |
91.208.167.0/24MOAS | No ROA | - | - |
1-10 of 124
1 / 13
Allocated Prefixes
(RIR)141Prefix | Country | RIR | Status |
|---|---|---|---|
| 31.223.160.0/20 | 🇳🇱 NL | RIPENCC | allocated |
| 37.17.208.0/20 | 🇳🇱 NL | RIPENCC | allocated |
| 78.108.128.0/20 | 🇳🇱 NL | RIPENCC | allocated |
| 80.246.192.0/20 | 🇳🇱 NL | RIPENCC | allocated |
| 80.255.240.0/20 | 🇳🇱 NL | RIPENCC | allocated |
| 81.21.136.0/21 | 🇳🇱 NL | RIPENCC | allocated |
| 81.30.32.0/20 | 🇳🇱 NL | RIPENCC | allocated |
| 85.10.160.0/19 | 🇳🇱 NL | RIPENCC | allocated |
| 91.208.167.0/24 | 🇳🇱 NL | RIPENCC | assigned |
| 171.33.128.0/21 | 🇳🇱 NL | RIPENCC | allocated |
1-10 of 141
1 / 15
All 124 announced prefixes of AS28878 →
BGP Neighbours
(seen in AS paths)Upstreams (2)
Networks AS28878 hands its own prefixes to: transit providers, or peers at an exchange.
ASPA
No ASPA
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
- ASPA explainedWhy AS28878 should publish an ASPA object
- 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/28878Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/28878" | jq