Skip to main content

AS41676

JMDI

ORG-JJM1-RIPE

Registry

Authoritative registration data

AS number
41676
Name
JMDI
Organisation
ORG-JJM1-RIPE
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

9

IPv6 prefixes

0

Total announced

9

Announced prefixes

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

Prefixes announced by AS41676
80.238.96.0/19 IPv4 /19 not checked
109.233.88.0/21 IPv4 /21 not checked
176.241.240.0/21 IPv4 /21 not checked
93.174.24.0/21 IPv4 /21 not checked
185.102.188.0/22 IPv4 /22 not checked
185.25.216.0/22 IPv4 /22 not checked
185.78.132.0/22 IPv4 /22 not checked
185.93.92.0/22 IPv4 /22 not checked
77.46.0.0/22 IPv4 /22 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 AS41676
Address families
EPIX.Warszawa 40,000 Mbps IPv4 · IPv6
Equinix Warsaw 40,000 Mbps IPv4
THINX Warsaw 40,000 Mbps IPv4
TPIX PL 10,000 Mbps IPv4
WRIX: WRIX 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 AS41676 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

5 networks seen before AS41676 in AS paths

Observed upstreams
Families
AS29535 88 1,062
v4
AS20804 ASN-TELENERGO 81 963
v4
AS9002 RETN-AS 56 720
v4
AS3356 LEVEL3 58 666
v4
AS8220 COLT 1 9
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS41676 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
AS49544 i3Dnet 1 18
v4
AS24482 SGGS-AS-AP 1 9
v4
AS28917 Fiord-AS 1 9
v4
AS36236 NETACTUATE 1 9
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.