Skip to main content

AS51784

X-CITY-AS

--------------------------------------------------

Registry

Authoritative registration data

AS number
51784
Name
X-CITY-AS
Organisation
--------------------------------------------------
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

3

IPv6 prefixes

1

Total announced

4

Announced prefixes

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

Prefixes announced by AS51784
46.63.0.0/18 IPv4 /18 not checked
46.63.64.0/18 IPv4 /18 not checked
185.177.188.0/22 IPv4 /22 not checked
2a03:69e0::/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 AS51784
Address families
DTEL-IX: PUBLIC 40,000 Mbps IPv4 · IPv6
Giganet IXN: Global exchange 30,000 Mbps IPv4
KM-IX old: Main 10,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 AS51784 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

6 networks seen before AS51784 in AS paths

Observed upstreams
Families
AS35297 194 489
v4
AS3326 236 438
v4 v6
AS199995 OT-AS 199 351
v4 v6
AS3255 136 213
v4 v6
AS3303 SWISSCOM 8 35
v4 v6
AS48648 1 1
v6

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS51784 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

4 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 12
v4 v6
AS49544 i3Dnet 1 8
v4 v6
AS48919 1 4
v4 v6
AS209823 1 4
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.