AS39310 NitroNet Nitronet sp. z o.o.
🇵🇱Org handle: ORG-NSZO8-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
3total
3 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)3,584
Announced (BGP)2,816
IPv6 Addresses
Allocated (RIR)7.9×10²⁸
Announced (BGP)0
Announced Prefixes
(BGP)3|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | - | |
| No ROA | RIPE | - | |
| Valid | RIPE | - |
Allocated Prefixes
(RIR)4Prefix | Country | RIR | Status |
|---|---|---|---|
| 79.98.144.0/21 | 🇵🇱 PL | RIPENCC | allocated |
| 185.56.188.0/22 | 🇵🇱 PL | RIPENCC | allocated |
| 195.90.106.0/23 | 🇵🇱 PL | RIPENCC | assigned |
| 2a02:e30::/32 | 🇵🇱 PL | RIPENCC | allocated |
All 3 announced prefixes of AS39310 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS39310 hands its own prefixes to: transit providers, or peers at an exchange.
- AS62081EPIX WAW GlobalMix Stowarzyszenie E Poludnie3
Downstreams (2)
Networks whose own prefixes AS39310 passes on: usually its customers.
Other adjacent networks (1)
Adjacent to AS39310 in the transit part of AS paths: peers, providers or customers.
- AS201054EPIX PolMix Stowarzyszenie E Poludnie1
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 AS39310 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/39310Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/39310" | jq