PJSC Rostelecom
AS42610 is PJSC Rostelecom (rt.ru). It announces 512,768 IPv4 addresses in 32 prefixes, and 2 IPv6 prefixes.
Russia· RIPE· allocated 2007-03-22· isp
Where its space is
The IPv4 it announces that IP Geolocation places, by country. A /24 counts for the AS announcing most of it.
- Russia512,768 · 100.00%
Registry record
Its ASN Whois record, as the registry publishes it.
- handle
- NCNET-AS
- name
- PJSC Rostelecom
- org
- ORG-JR8-RIPE
- org name
- PJSC Rostelecom
- org address
- 14 A, Sinopskaya nabereznaya, 191167, S.Peterburg, RUSSIAN FEDERATION
- org country
- RU
- country
- RU
- source
- ripe
- status
- ASSIGNED
- created
- 2007-03-22
- updated
- 2026-08-17
- descr
- OJSC "National Cable Networks"
- remarks
- Upstreams / Clients / Direct Peers / | NCNET filters out | / | inbound prefixes longer than /24 | / | MEDs are overwritten | / | unless special arrangements have been made | / | COMMUNITIES | / | Communities sent to downstreams are marked upon | / | upsteam type and place of interconnection. | / | 42610:yyyy (4 digits) | / | User-settable communities are derived from | / | UPLINKS, PEERS and SPECIAL communities | / | 42610:yyyyx (with 5th digit) | / | where 'x' is: | / | ....x=9 - advertise without prepends
- maintainer
- RIPE-NCC-END-MNT|ROSTELECOM-MNT
- abuse name
- PJSC Rostelecom Technical Team
- abuse email
- abuse@rt.ru
- abuse kind
- role
What the databases see
Addresses each address-keyed database holds in the IPv4 it announces, as a share of that space, with its largest providers. Counts overlap.
- VPN IP38,149vpngate, best_proxy_switcher, ideco_ru7.44%
- Residential Proxy IP24,484geonode, geonix, proxyseller4.77%
- None here
- floppydata, dataimpulse0.01%
- Tor IP120.00%
- None here
- Hosting IP222,97643.48%
- None here
- None here
- None here
- SSH IP10,6202.07%
- SMTP IP1770.03%
- DNS Resolver IP1,4350.28%
IPv4 prefixes
Every IPv4 prefix BGP Route saw it announce. A prefix another AS also announces says so.
| PREFIX | COUNTRY | RPKI | PEERS | FIRST SEEN |
|---|---|---|---|---|
| 5.228.0.0/16 | Russia | valid | 18 | 2026-10-02 |
| 5.228.80.0/23 | Russia | valid | 18 | 2026-10-02 |
| 5.228.82.0/23 | Russia | valid | 18 | 2026-10-02 |
| 5.228.112.0/23 | Russia | valid | 18 | 2026-10-02 |
| 5.228.114.0/23 | Russia | valid | 18 | 2026-10-02 |
| 5.228.116.0/23 | Russia | valid | 18 | 2026-10-02 |
| 5.228.118.0/23 | Russia | valid | 18 | 2026-10-02 |
| 37.110.0.0/17 | Russia | valid | 18 | 2026-10-02 |
| 37.110.128.0/19 | Russia | valid | 18 | 2026-10-02 |
| 37.204.0.0/16 | Russia | valid | 18 | 2026-10-02 |
| 46.242.0.0/17 | Russia | valid | 18 | 2026-10-02 |
| 46.242.8.0/22 | Russia | valid | 18 | 2026-10-02 |
| 46.242.12.0/22 | Russia | valid | 18 | 2026-10-02 |
| 77.37.128.0/17 | Russia | valid | 18 | 2026-10-02 |
| 83.166.227.0/24 | Russia | valid | 18 | 2026-10-02 |
| 84.253.64.0/18 | Russia | valid | 18 | 2026-10-02 |
| 85.30.192.0/18 | Russia | valid | 18 | 2026-10-02 |
| 85.172.171.0/24 | Russia | valid | 1 | 2026-10-02 |
| 87.240.40.0/21 | Russia | not found | 18 | 2026-10-02 |
| 87.240.48.0/20 | Russia | not found | 18 | 2026-10-02 |
| 90.154.64.0/18 | Russia | valid | 18 | 2026-10-02 |
| 90.154.70.0/23 | Russia | valid | 18 | 2026-10-02 |
| 90.154.72.0/23 | Russia | valid | 18 | 2026-10-02 |
| 90.156.172.0/22 | Russia | valid | 18 | 2026-10-02 |
| 95.84.128.0/18 | Russia | valid | 18 | 2026-10-02 |
| 95.84.192.0/18 | Russia | valid | 18 | 2026-10-02 |
| 109.173.0.0/17 | Russia | valid | 18 | 2026-10-02 |
| 178.140.0.0/16 | Russia | valid | 18 | 2026-10-02 |
| 185.19.20.0/22 | Russia | valid | 18 | 2026-10-02 |
| 188.32.0.0/16 | Russia | valid | 18 | 2026-10-02 |
| 188.255.0.0/17 | Russia | valid | 18 | 2026-10-02 |
| 217.12.41.0/24 | Russia | valid | 18 | 2026-10-02 |
IPv6 prefixes
Every IPv6 prefix BGP Route saw it announce.
Test the real build first.
An evaluation license puts a full current build in your hands — every row, every column, no sampling — so you can measure it against your own traffic before anyone talks about terms.