Skip to main content

AS56690

VNET-LLC-AS

VNET LLC

Registry

Authoritative registration data

AS number
56690
Name
VNET-LLC-AS
Organisation
VNET LLC
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

18

IPv6 prefixes

1

Total announced

19

Announced prefixes

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

Prefixes announced by AS56690
193.233.176.0/20 IPv4 /20 not checked
185.250.60.0/22 IPv4 /22 not checked
193.233.212.0/22 IPv4 /22 not checked
193.233.224.0/22 IPv4 /22 not checked
193.233.240.0/22 IPv4 /22 not checked
193.233.92.0/22 IPv4 /22 not checked
91.226.172.0/22 IPv4 /22 not checked
193.233.12.0/23 IPv4 /23 not checked
193.233.166.0/23 IPv4 /23 not checked
193.233.168.0/23 IPv4 /23 not checked
193.233.24.0/23 IPv4 /23 not checked
193.233.26.0/23 IPv4 /23 not checked
193.233.28.0/23 IPv4 /23 not checked
193.233.54.0/23 IPv4 /23 not checked
109.248.35.0/24 IPv4 /24 not checked
193.233.150.0/24 IPv4 /24 not checked
193.233.73.0/24 IPv4 /24 not checked
193.39.116.0/24 IPv4 /24 not checked
2a09:8880::/36 IPv6 /36 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 AS56690
Address families
GNM-IX 200,000 Mbps IPv4 · IPv6
Global-IX 100,000 Mbps IPv4 · IPv6
PITER-IX Frankfurt 50,000 Mbps IPv4
PITER-IX Helsinki 50,000 Mbps IPv4
PITER-IX Moscow: MSK_PEERING_VLAN 50,000 Mbps IPv4 · IPv6
PITER-IX Saint-Petersburg: SPB_PEERING_VLAN 50,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 AS56690 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

13 networks seen before AS56690 in AS paths

Observed upstreams
Families
AS35598 340 3,439
v4 v6
AS31500 205 2,353
v4 v6
AS62255 BEMYLINK 54 786
v4
AS8218 NEO-ASN 2 127
v4 v6
AS25091 IP-Max 4 114
v4 v6
AS47692 2 72
v4 v6
AS9198 2 20
v4 v6
AS6663 1 18
v4 v6
AS60171 1 18
v4 v6
AS137409 GSLNETWORKS-AS-AP 1 18
v4
AS6204 1 17
v4
AS15958 1 17
v4
AS42295 TBISS-AS 1 17
v4

No rows match “”.

Showing of

Observed downstreams

1 networks seen after AS56690 in AS paths

Observed downstreams
Families
AS200722 40 45
v4

No rows match “”.

Showing of

Uncertain adjacencies

18 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 95
v4 v6
AS49544 i3Dnet 1 36
v4
AS205112 PHILUNET 2 20
v4 v6
AS37721 ORG-VTS1-AFRINIC 2 19
v4
AS41327 FIBERTELECOM-AS 1 19
v4 v6
AS49434 1 19
v4 v6
AS209823 1 19
v4 v6
AS13004 2 18
v4
AS49673 TRUENETWORK 2 18
v4
AS208972 2 18
v4
AS3170 1 18
v4 v6
AS29049 1 18
v4
AS199524 GCORE 1 18
v4
AS44901 1 17
v4
AS51185 MAINSTREAMING-AS 1 17
v4
AS200612 GulfBridgeInternational 1 17
v4
AS28910 1 1
v6
AS41722 1 1
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.