Skip to main content

AS207301

JACKMX

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

Registry

Authoritative registration data

AS number
207301
Name
JACKMX
Organisation
---------------------------------------------
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

4

Total announced

6

Announced prefixes

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

Prefixes announced by AS207301
44.30.72.0/24 IPv4 /24 not checked
91.197.70.0/24 IPv4 /24 not checked
2a0c:b641:780::/44 IPv6 /44 not checked
2a0c:b641:780::/48 IPv6 /48 not checked
2a0c:b641:781::/48 IPv6 /48 not checked
2a0c:b641:782::/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 AS207301
Address families
4b42 Internet Exchange Point: Switzerland 1,000 Mbps IPv6
BEE-IX 20,000 Mbps IPv6
LVIV-IX: Main 20,000 Mbps IPv4 · IPv6
RUDAKI-IX 20,000 Mbps IPv4 · IPv6
ixFabric - Amsterdam 1,000 Mbps 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 AS207301 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

6 networks seen before AS207301 in AS paths

Observed upstreams
Families
AS30886 KOMITEX-AS 30,634 134,302
v4 v6
AS8772 NLineLLC 17,310 99,207
v6
AS48648 KYIVLINK 5,291 17,335
v4 v6
AS211509 RUDAKI-AS 1,805 5,022
v4 v6
AS3 MIT-GATEWAYS 1 4
v6
AS29632 NASSIST-AS 1 4
v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS207301 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

18 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.