is down


our gatling project is downloading artefacts from this repository

It has been working fine until yesterday and started to fail since. The repository web site appears to be down.

I guess I can use another repository however I was wondering if there are any plans for this repository to be back up?


Hi Natalia,

I just sent an email to our sysadmin.
I hope he’ll be able to restart soon.



Great, thanks Stephane!

Best wishes,

Hi Stephane,

I am experiencing the same issue as Natalie mentioned.
I am afraid to tell you that the issue is not yet resolved as my gatling job is still complaining about connection to
Can you please help? Or is there another repository that I can configure gatling to use?



Our sysadmin is a late waker…
The repository is up again.

Note that at some point in the future, we’ll no longer host Gatling 1 artifacts as Gatling 2 ones are in maven central.



Sorry, false good news.

The problem is that our company router is dead. We’re supposed to receive a new one today…
Will let you know.

Thanks Stephane,

we are archiving the artifacts in a local repository. I am aware you will stop support when Gatling 2 is officially released. Just give us enough heads up so we can make sure we migrate before that happens.


Hi all,

I have the same problem like you and i’am waiting for this new router :slight_smile:
Good luck Stephane


We’ll also be moving the repository to a new host too, in case the router doesn’t make it on time.
For backup reasons, I had to take down very old artifacts.

We’ll only be hosting the last version of each series: 1.4.7, 1.5.6 and 2M3a.
Upgrading old 1.4.x to 1.4.7 and old 1.5.x to 1.5.6 should be pretty straightforward.
2M1 and 2M2 were definitively too old and I really hope no one use them anymore.

So once the repo is up again, don’t forget to update your poms (or what ever you use).


Stéphane is back!

Great, thank you! My test suite is running again.

Best wishes,

Thanks a lot.
Have a nice weekend.


I’m on the west coast of the US and I’m still seeing it not responding to pings.

[~]$ ping

PING ( 56 data bytes

Request timeout for icmp_seq 0

Request timeout for icmp_seq 1

Request timeout for icmp_seq 2

Request timeout for icmp_seq 3

^C ping statistics —

5 packets transmitted, 0 packets received, 100.0% packet loss

Could this be a DNS update issue?



We changed host so it might take some time to propagate DNS.