Evolink EAD
AS8262 is Evolink EAD (evolink.com). It announces 34,560 IPv4 addresses in 33 prefixes, and 2 IPv6 prefixes.
Bulgaria· RIPE· allocated 1997-04-08· 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.
- Bulgaria34,048 · 98.52%
- United Kingdom512 · 1.48%
Registry record
Its ASN Whois record, as the registry publishes it.
- handle
- EVOLINK-AS
- name
- Evolink EAD
- org
- ORG-NAL1-RIPE
- org name
- Evolink EAD
- org address
- 16V Barzaritsa str., 1618, Sofia, BULGARIA
- org country
- BG
- country
- BG
- source
- ripe
- status
- ASSIGNED
- created
- 2001-10-02
- updated
- 2017-11-15
- remarks
- Please send any abuse reports to abuse@evolink.com / For peering questions to peering@evolink.com / For any other issues use support@evolink.com / - RFC1918 and other reserved networks and subnet / are not permitted. / - Advertisements with reserved ASes in the path / (ie 64512 - 65535) are not permitted. / - Prefixes shorter than /8 or longer than /24 are / not permitted. / - Localpref will be set to 300 by default, subject / to modification based on received communities as / outlined below. / - A hard lim
- maintainer
- RIPE-NCC-END-MNT|AS8262-MNT
- abuse name
- Lirex Net Abuse Contact
- abuse email
- abuse@evolink.com
- 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 IP304watchguard, stormshield0.88%
- anyip, proxyrack, proxyseller0.04%
- None here
- None here
- None here
- None here
- Hosting IP6,40018.52%
- None here
- None here
- None here
- SSH IP1300.38%
- SMTP IP390.11%
- 0.20%
IPv4 prefixes
Every IPv4 prefix BGP Route saw it announce. A prefix another AS also announces says so.
| PREFIX | COUNTRY | RPKI | PEERS | FIRST SEEN |
|---|---|---|---|---|
| 82.119.64.0/19 | Bulgaria | valid | 17 | 2026-10-02 |
| 82.119.68.0/24 | United Kingdom | valid | 17 | 2026-10-02 |
| 82.119.69.0/24 | United Kingdom | valid | 17 | 2026-10-02 |
| 82.119.80.0/21 | Bulgaria | valid | 17 | 2026-10-02 |
| 82.119.83.0/24 | Bulgaria | valid | 17 | 2026-10-02 |
| 82.119.84.0/24 | Bulgaria | valid | 17 | 2026-10-02 |
| 82.119.94.0/24 | Bulgaria | valid | 17 | 2026-10-02 |
| 85.14.0.0/18 | Bulgaria | valid | 17 | 2026-10-02 |
| 85.14.0.0/23 | Bulgaria | valid | 17 | 2026-10-02 |
| 85.14.12.0/24 | Bulgaria | valid | 17 | 2026-10-02 |
| 85.14.13.0/24 | Bulgaria | valid | 6 | 2026-10-02 |
| 85.14.21.0/24 | Bulgaria | valid | 17 | 2026-10-02 |
| 85.14.24.0/24 | Bulgaria | valid | 17 | 2026-10-02 |
| 85.14.30.0/24 | Bulgaria | valid | 17 | 2026-10-02 |
| 85.14.44.0/24 | Bulgaria | valid | 17 | 2026-10-02 |
| 85.14.49.0/24 | Bulgaria | valid | 17 | 2026-10-02 |
| 89.252.192.0/22 | Bulgaria | valid | 17 | 2026-10-02 |
| 89.252.199.0/24 | Bulgaria | valid | 17 | 2026-10-02 |
| 89.252.200.0/21 | Bulgaria | valid | 17 | 2026-10-02 |
| 89.252.208.0/20 | Bulgaria | valid | 17 | 2026-10-02 |
| 89.252.223.0/24 | Bulgaria | valid | 17 | 2026-10-02 |
| 89.252.224.0/19 | Bulgaria | valid | 17 | 2026-10-02 |
| 89.252.229.0/24 | Bulgaria | valid | 17 | 2026-10-02 |
| 89.252.241.0/24 | Bulgaria | valid | 17 | 2026-10-02 |
| 89.252.246.0/24 | Bulgaria | valid | 17 | 2026-10-02 |
| 176.67.233.0/24 | Bulgaria | valid | 17 | 2026-10-02 |
| 176.67.234.0/24 | Bulgaria | valid | 17 | 2026-10-02 |
| 185.92.132.0/22 | Bulgaria | valid | 17 | 2026-10-02 |
| 194.12.224.0/19 | Bulgaria | valid | 17 | 2026-10-02 |
| 194.12.244.0/24 | Bulgaria | valid | 17 | 2026-10-02 |
| 194.12.254.0/24 | Bulgaria | valid | 17 | 2026-10-02 |
| 194.50.76.0/24 | Bulgaria | not found | 17 | 2026-10-02 |
| 217.168.232.0/24 | Bulgaria | valid | 17 | 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.