AS47453 ITSERVICE ITservice 2009 LTD
🇧🇬Org handle: ORG-ML96-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
6total
5 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)1,280
Announced (BGP)1,280
IPv6 Addresses
Allocated (RIR)1.2×10²⁴
Announced (BGP)1.2×10²⁴
Announced Prefixes
(BGP)6|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)6Prefix | Country | RIR | Status |
|---|---|---|---|
| 85.118.94.0/24 | 🇧🇬 BG | RIPE | assigned |
| 85.118.95.0/24 | 🇧🇬 BG | RIPE | assigned |
| 87.246.47.0/24 | 🇧🇬 BG | RIPE | assigned |
| 87.246.48.0/24 | 🇧🇬 BG | RIPE | assigned |
| 87.246.49.0/24 | 🇧🇬 BG | RIPE | assigned |
| 2001:678:904::/48 | 🇧🇬 BG | RIPENCC | assigned |
All 6 announced prefixes of AS47453 →
BGP Neighbours
(seen in AS paths)Upstreams (3)
Networks AS47453 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (1)
Networks whose own prefixes AS47453 passes on: usually its customers.
- AS20657ATLANTIS BG2
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 AS47453 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/47453Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/47453" | jq