AS47379 SITS-AS SITS Ltd
π·πΊOrg handle: ORG-SL259-RIPE
Moscow, Russia
RIPE NCCallocated
Announced Prefixes (BGP)
3total
3 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)1,792
Announced (BGP)1,792
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)0
Prefix Limit (IPv4)
10
Prefix Limit (IPv6)
5
Country
π·πΊ RURIR
RIPE NCCStatus
allocated
Allocated
2008-06-10
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 |
|---|---|---|---|
| 91.204.108.0/22 | π·πΊ RU | RIPENCC | assigned |
| 91.238.244.0/23 | π·πΊ RU | RIPENCC | assigned |
| 194.110.253.0/24 | π·πΊ RU | RIPENCC | assigned |
All 3 announced prefixes of AS47379 β
BGP Neighbours
(seen in AS paths)Upstreams (2)
Networks AS47379 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (2)
Networks whose own prefixes AS47379 passes on: usually its customers.
Other adjacent networks (1)
Adjacent to AS47379 in the transit part of AS paths: peers, providers or customers.
- AS1299TWELVE99 Arelion Sweden AB2
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 AS47379 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/47379Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/47379" | jq