Skip to main content

AS205784

NV-Tel

NV Telecom LLC

Registry

Authoritative registration data

AS number
205784
Name
NV-Tel
Organisation
NV Telecom LLC
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

4

IPv6 prefixes

0

Total announced

4

Announced prefixes

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

Prefixes announced by AS205784
213.109.145.0/24 IPv4 /24 not checked
88.210.29.0/24 IPv4 /24 not checked
88.210.49.0/24 IPv4 /24 not checked
94.142.248.0/24 IPv4 /24 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 AS205784
Address families
PITER-IX Frankfurt 20,000 Mbps IPv4
PITER-IX Helsinki 20,000 Mbps IPv4
PITER-IX Kiev 20,000 Mbps IPv4
PITER-IX Saint-Petersburg: SPB_PEERING_VLAN 20,000 Mbps IPv4

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 AS205784 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

7 networks seen before AS205784 in AS paths

Observed upstreams
Families
AS48293 UNIONTEL-RU-AS 244 1,340
v4
AS28917 Fiord-AS 18 76
v4
AS25091 IP-Max 5 36
v4
AS49434 FBWNETWORKS 2 8
v4
AS137409 GSLNETWORKS-AS-AP 1 8
v4
AS9198 KAZTELECOM-AS 1 4
v4
AS21030 CDNNOW-AS 1 4
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS205784 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

6 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 28
v4
AS28910 INTAL-ASN 1 4
v4
AS37721 ORG-VTS1-AFRINIC 1 4
v4
AS41722 MIRAN-AS 1 4
v4
AS199524 GCORE 1 4
v4
AS205112 PHILUNET 1 4
v4

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.