Skip to main content

AS39288

VTELECOM

--- NETTE backup ---

Registry

Authoritative registration data

AS number
39288
Name
VTELECOM
Organisation
--- NETTE backup ---
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

6

IPv6 prefixes

1

Total announced

7

Announced prefixes

Observed in BGP by route collectors, not a registry allocation list

Prefixes announced by AS39288
46.21.208.0/20 IPv4 /20 not checked
94.232.152.0/21 IPv4 /21 not checked
158.255.88.0/22 IPv4 /22 not checked
158.255.92.0/23 IPv4 /23 not checked
158.255.94.0/24 IPv4 /24 not checked
193.138.118.0/24 IPv4 /24 not checked
2a02:2928::/32 IPv6 /32 not checked

No rows match “”.

Showing of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS39288
Address families
EPIX.Warszawa 10,000 Mbps IPv4 · IPv6

No rows match “”.

Showing of

Source:peeringdb retrieved

Exchange membership means the network has a listed connection; it does not prove peering with other members.

Observed adjacencies

Networks seen next to AS39288 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

5 networks seen before AS39288 in AS paths

Observed upstreams
Families
AS62081 1,957 7,992
v4 v6
AS56391 69 273
v4
AS12912 11 90
v4
AS201054 14 84
v4
AS20473 2 2
v6

No rows match “”.

Showing of

Observed downstreams

5 networks seen after AS39288 in AS paths

Observed downstreams
Families
AS12346 LUBMAN-COM-AS 677 4,706
v4
AS43962 383 668
v4 v6
AS197910 289 381
v4
AS42520 189 240
v4
AS206282 6 9
v4

No rows match “”.

Showing of

Uncertain adjacencies

3 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 5 133
v4 v6
AS49544 i3Dnet 5 42
v4 v6
AS36236 NETACTUATE 5 23
v4 v6

No rows match “”.

Showing of

Note:
These are observed adjacencies derived from BGP path data, not confirmed commercial relationships. A network appearing before another in an AS path does not establish that it is a paying transit customer, a settlement free peer, or anything else contractual. Adjacencies marked uncertain were seen only as direct peers of a route collector, so the collector's own peering may have created them.