Skip to main content

AS395502

JCOLO

JeffColo

Registry

Authoritative registration data

AS number
395502
Name
JCOLO
Organisation
JeffColo
Country
RIR
ARIN
Registered
Source:asn:rdap retrieved

IPv4 prefixes

3

IPv6 prefixes

4

Total announced

7

Announced prefixes

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

Prefixes announced by AS395502
23.171.112.0/24 IPv4 /24 not checked
23.175.0.0/24 IPv4 /24 not checked
23.175.1.0/24 IPv4 /24 not checked
2607:9280:1::/48 IPv6 /48 not checked
2607:9280:2::/48 IPv6 /48 not checked
2607:9280:a::/48 IPv6 /48 not checked
2607:9280:b::/48 IPv6 /48 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 AS395502
Address families
FCIX 10,000 Mbps IPv4 · IPv6
JXIX 10,000 Mbps IPv4 · IPv6
NWAX: Primary Peering VLAN 10,000 Mbps IPv4 · IPv6
PR-IX: Main 210,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 AS395502 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

8 networks seen before AS395502 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 998 3,575
v4 v6
AS21559 918 1,916
v4 v6
AS6461 ZAYO-6461 130 429
v4 v6
AS20055 AS-WHOLESAIL 119 369
v4 v6
AS11404 18 35
v4 v6
AS18895 7 7
v4
AS58057 SECUREBIT 1 2
v4 v6
AS398447 1 2
v4 v6

No rows match “”.

Showing of

Observed downstreams

3 networks seen after AS395502 in AS paths

Observed downstreams
Families
AS34553 666 2,261
v4 v6
AS20940 AKAMAI-ASN1 354 743
v4 v6
AS63293 353 741
v4 v6

No rows match “”.

Showing of

Uncertain adjacencies

1 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS36236 NETACTUATE 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.