Skip to main content

AS25837

DATALINK-IT

DATALINK INFORMATION TECHNOLOGIES INC.

Registry

Authoritative registration data

AS number
25837
Name
DATALINK-IT
Organisation
DATALINK INFORMATION TECHNOLOGIES INC.
Country
—
RIR
ARIN
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

0

Total announced

2

Announced prefixes

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

Prefixes announced by AS25837
192.65.230.0/23 IPv4 /23 not checked
38.89.164.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 AS25837
Address families
FL-IX 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 AS25837 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

8 networks seen before AS25837 in AS paths

Observed upstreams
Families
AS174 COGENT-174 193 433
v4
AS33132 ZAYO-CCF-AS33132 61 180
v4
AS6939 HURRICANE 21 23
v4
AS3303 SWISSCOM 7 9
v4
AS137409 GSLNETWORKS-AS-AP 4 4
v4
AS4230 ASN4230 2 2
v4
AS61568 ASN61568 1 1
v4
AS64126 64126 1 1
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS25837 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

12 adjacencies that may be an artefact of collector peering

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.