AS59815 TRINITY-AS Trinity Ltd
๐ท๐บOrg handle: ORG-TL979-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
16total
16 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)43,520
Announced (BGP)44,544
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)0
Prefix Limit (IPv4)
50
Prefix Limit (IPv6)
5
Country
๐ท๐บ RURIR
RIPE NCCStatus
allocated
Allocated
2014-09-18
Announced Prefixes
(BGP)16|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| No ROA | RIPE | 2026-10-10 | |
| No ROA | RIPE | 2026-10-10 | |
| No ROA | RIPE | 2026-10-10 | |
| No ROA | RIPE | 2026-10-10 | |
| No ROA | RIPE | 2026-10-10 | |
| No ROA | RIPE | 2026-10-10 | |
| No ROA | RIPE | 2026-10-10 | |
| No ROA | RIPE | 2026-10-10 | |
| No ROA | RIPE | 2026-10-10 | |
| No ROA | RIPE | 2026-10-10 |
1-10 of 16
1 / 2
Allocated Prefixes
(RIR)13Prefix | Country | RIR | Status |
|---|---|---|---|
| 5.104.32.0/19 | ๐ท๐บ RU | RIPENCC | allocated |
| 5.104.32.0/20 | ๐ท๐บ RU | RIPE | assigned |
| 5.104.48.0/20 | ๐ท๐บ RU | RIPE | assigned |
| 31.6.96.0/19 | ๐ท๐บ RU | RIPENCC | allocated |
| 31.6.96.0/20 | ๐ท๐บ RU | RIPE | assigned |
| 31.6.112.0/20 | ๐ท๐บ RU | RIPE | assigned |
| 109.75.192.0/20 | ๐ท๐บ RU | RIPENCC | allocated |
| 178.209.88.0/21 | ๐ท๐บ RU | RIPENCC | allocated |
| 178.209.92.0/22 | ๐ท๐บ RU | RIPE | assigned |
| 185.42.40.0/22 | ๐ท๐บ RU | RIPENCC | allocated |
1-10 of 13
1 / 2
All 16 announced prefixes of AS59815 โ
BGP Neighbours
(seen in AS paths)Upstreams (4)
Networks AS59815 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (1)
Networks whose own prefixes AS59815 passes on: usually its customers.
- AS25299TRINITY10
Transfer History
Registry transfers of AS59815 between organisations.
- AS59815Transfer ยท
- AS59815Transfer ยท
| Date | Resource | From | To | Type |
|---|---|---|---|---|
| AS59815 | Kompeatelecom Ltd. | Trinity Ltd | Transfer | |
| AS59815 | TRK Metro LLC | Kompeatelecom Ltd. | Transfer |
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 AS59815 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/59815Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/59815" | jq