AS49712 TBM-AS JSC "TBM"
🇷🇺Org handle: ORG-ZA46-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
1total
1 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)256
Announced (BGP)256
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)0
Routing hygiene
Score 40/100 · Medium riskRPKI ROA coverage
0%
no RPKI invalid prefixes
IRR route objects
100%
no origin mismatches
Hijack signals
0
0 announced against others' ROAs, 0 own announced by others
Upstreams
1
diversity 0/100
- 100% of announced prefixes (1 of 1) have no valid ROA
- Only one upstream seen in the AS paths of its routes
Based on 1 announced prefix, updated daily (2026-10-12). How the score works · RPKI explained
Announced Prefixes
(BGP)1|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| No ROA | RIPE | 2026-10-12 |
Allocated Prefixes
(RIR)1Prefix | Country | RIR | Status |
|---|---|---|---|
| 91.213.184.0/24 | 🇷🇺 RU | RIPENCC | assigned |
All 1 announced prefix of AS49712 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS49712 hands its own prefixes to: transit providers, or peers at an exchange.
- AS8470MAcomnet JSC Macomnet1
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 AS49712 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/49712Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/49712" | jq