AS203733 itpartner-no BINERO TROMSO AS
🇳🇴Org handle: ORG-IPTA3-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
3total
3 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)1,280
Announced (BGP)768
IPv6 Addresses
Allocated (RIR)6.3×10²⁹
Announced (BGP)0
Announced Prefixes
(BGP)3|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| No ROA | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)3Prefix | Country | RIR | Status |
|---|---|---|---|
| 185.125.160.0/22 | 🇳🇴 NO | RIPENCC | allocated |
| 185.125.162.0/24 | 🇳🇴 NO | RIPE | assigned |
| 2a06:bd00::/29 | 🇳🇴 NO | RIPENCC | allocated |
All 3 announced prefixes of AS203733 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS203733 hands its own prefixes to: transit providers, or peers at an exchange.
- AS2119TELENOR NORGE Telenor Norge AS3
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 AS203733 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/203733Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/203733" | jq