AS35196 IH-TRANSIT-AS FIRST SERVER LIMITED
🇬🇧Org handle: ORG-FA790-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
14total
2 IPv412 IPv6
IPv4 Addresses
Allocated (RIR)0
Announced (BGP)512
IPv6 Addresses
Allocated (RIR)1.2×10²⁴
Announced (BGP)3.9×10²⁹
Announced Prefixes
(BGP)14|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
185.5.250.0/24MOAS | Invalid | - | 2026-10-11 |
195.47.250.0/24MOAS | Valid | - | 2026-10-11 |
2a09:5302::/32MOAS | Valid | - | 2026-10-11 |
| Valid | RIPE | 2026-10-11 | |
2a0a:9300:2::/48MOAS | Valid | - | 2026-10-11 |
| Valid | - | 2026-10-11 | |
| Valid | - | 2026-10-11 | |
| Valid | - | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
2a0a:9302:1::/48MOAS | Valid | - | 2026-10-11 |
1-10 of 14
1 / 2
Allocated Prefixes
(RIR)1Prefix | Country | RIR | Status |
|---|---|---|---|
| 2a0a:9300:1000::/48 | 🇷🇺 RU | RIPE | assigned |
All 14 announced prefixes of AS35196 →
BGP Neighbours
(seen in AS paths)Upstreams (5)
Networks AS35196 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (4)
Networks whose own prefixes AS35196 passes on: usually its customers.
Transfer History
Registry transfers of AS35196 between organisations.
- AS35196Transfer ·
- AS35196Transfer ·
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 AS35196 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/35196Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/35196" | jq