Skip to main content

AS395853

NYCMESH

NYC Mesh Inc.

Registry

Authoritative registration data

AS number
395853
Name
NYCMESH
Organisation
NYC Mesh Inc.
Country
RIR
ARIN
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 AS395853
199.167.59.0/24 IPv4 /24 not checked
199.170.132.0/24 IPv4 /24 not checked
208.68.5.0/24 IPv4 /24 not checked
23.158.16.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 AS395853
Address families
DE-CIX New York: DE-CIX New York Peering LAN 10,000 Mbps IPv4 · IPv6
MegaIX New York 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 AS395853 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

8 networks seen before AS395853 in AS paths

Observed upstreams
Families
AS46450 PILOT 273 1,011
v4
AS27257 246 341
v4
AS25091 IP-Max 5 9
v4
AS34549 MEER-AS 5 6
v4
AS137409 GSLNETWORKS-AS-AP 3 4
v4
AS33891 CORE-BACKBONE 2 3
v4
AS4230 ASN4230 1 1
v4
AS37468 ORG-AC4-AFRINIC 1 1
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS395853 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

11 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS14840 ASN14840 1 4
v4
AS24482 SGGS-AS-AP 1 3
v4
AS49544 i3Dnet 1 2
v4
AS1828 UNITAS 1 1
v4
AS22652 1 1
v4
AS35280 F5 1 1
v4
AS37721 ORG-VTS1-AFRINIC 1 1
v4
AS41327 FIBERTELECOM-AS 1 1
v4
AS45489 SLT-GLOBAL 1 1
v4
AS199524 GCORE 1 1
v4
AS264479 1 1
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.