AS210632 NOVARA-AS Justin Baasch
🇩🇪Org handle: ORG-NITS4-RIPE
Novara Network
RIPE NCCallocated
Announced Prefixes (BGP)
4total
0 IPv44 IPv6
IPv4 Addresses
Allocated (RIR)0
Announced (BGP)0
IPv6 Addresses
Allocated (RIR)3×10²⁶
Announced (BGP)4.8×10²⁴
Routing hygiene
Score 34/100 · Medium riskRPKI ROA coverage
0%
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
3
diversity 63/100
- 100% of announced prefixes (4 of 4) have no valid ROA
Based on 4 announced prefixes, updated daily (2026-10-24). How the score works · RPKI explained
Announced Prefixes
(BGP)4|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| No ROA | RIPE | 2026-10-25 | |
| No ROA | RIPE | 2026-10-25 | |
| No ROA | RIPE | 2026-10-25 | |
| No ROA | RIPE | 2026-10-25 |
Allocated Prefixes
(RIR)1Prefix | Country | RIR | Status |
|---|---|---|---|
| 2a0b:4e07:6100::/40 | 🇩🇪 DE | RIPE | assigned |
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 AS210632 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/210632Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/210632" | jq