AS34187 ASPA Check - RENOME Service
PublishedRENOME-AS LLC Renome-Service🇺🇦 - ASPA check for AS34187: the upstream transit providers AS34187 has authorized in its RPKI Autonomous System Provider Authorization (ASPA) object, and the networks that list AS34187 as their provider. Routers that validate ASPA use these records to detect route leaks in BGP paths.
How to read this ASPA check
The 11 providers below are the only networks allowed to appear directly above AS34187 in an AS-path. If AS34187 uses a transit provider that is missing from this list, routers that enforce ASPA treat its routes through that provider as invalid, so the list should include every current and backup transit provider. Peers do not belong in it.
Step-by-step ASPA check guide - including how to validate an AS-path hop by hop.
Peering Topology
Upstream Providers(11)
AS34187 authorizes these ASNs as upstream transit providers.
| ASN | Name |
|---|---|
| AS174 | 🇺🇸COGENT-174 - Cogent Communications, LLC |
| AS3255 | 🇺🇦UARNET-AS LLC EKSINTECH |
| AS6939 | 🇺🇸HURRICANE - Hurricane Electric LLC |
| AS9002 | 🇬🇧RETN-AS RETN Limited |
| AS31210 | 🇺🇦DTEL-IX-AS Digital Telecom IX LLC |
| AS35297 | 🇺🇦DATALINE-AS Dataline LLC |
| AS44600 | 🇺🇦GT-AS "GIGATRANS UKRAINE", LLC |
| AS59613 | 🇺🇦UBNIX Ukrainian Backbone Networks LLC |
| AS60812 | 🇺🇦IXP-1-IX-UA "1-IX" LLC |
| AS62041 | 🇻🇬Telegram Telegram Messenger Inc |
Downstream Customers(1)
These ASNs list AS34187 as an authorized upstream provider.
| ASN | Name |
|---|---|
| AS15713 | 🇺🇦GCN-UA LLC Global-City-Net |
ASPA object expires: 2026-10-27
Related Tools and Guides
- How to run an ASPA check - read and verify an ASPA record step by step
- ASPA explained - how provider authorization stops route leaks
- ASPA Check tool - check the ASPA record of any other ASN
- RPKI & ROA Lookup - validate prefixes and check ASPA records for any ASN
- Global ASPA Adoption Statistics - transit-free ASNs, top upstream providers, adoption trends
- AS34187 Overview - prefixes, BGP routes, peers, and RPKI status