General "Epic Masterserver is down!" thread.
Posted: Sun Sep 24, 2017 4:42 pm
WHAAAaaaa
The Epic Games masterserver is offline/doesn't work anymore!
Now we all got that off our chests, I would like to share my observation that the Epic Games masterserver stopped accepting connections earlier today, at 0500h GMT.
This comes as no surprise.
This happened last year (and picture below)
This happened the year before
And now it happened this year.
What happens next? If empirical data is reliable, the masterserver should be online shortly and accepting connections again soon as in the figure below.
In the meanwhile, consider migrating to one of the 333networks masterservers.
Psst! We have a new version coming soon!
The Epic Games masterserver is offline/doesn't work anymore!
Spoiler
PANIC PANIC PANIC PANIC PANIC PANIC PANIC PANIC PANIC PANIC PANIC
Above: the number of servers found at Epic's masterserver and the failures today.
Code: Select all
[2017-09-23 17:13:34] [applet-rx] found 634 addresses at 199.255.40.174 for ut.
[2017-09-23 18:13:34] [applet-rx] found 637 addresses at 199.255.40.174 for ut.
[2017-09-23 19:13:34] [applet-rx] found 630 addresses at 199.255.40.174 for ut.
[2017-09-23 20:13:34] [applet-rx] found 634 addresses at 199.255.40.174 for ut.
[2017-09-23 21:13:34] [applet-rx] found 633 addresses at 199.255.40.174 for ut.
[2017-09-23 22:13:34] [applet-rx] found 633 addresses at 199.255.40.174 for ut.
[2017-09-23 23:13:34] [applet-rx] found 628 addresses at 199.255.40.174 for ut.
darkelarious@m5a-333networks:/mnt/deimos/web/333networks/log$ cat MasterServer-2017-week39.log | grep 199.255.40.174
[2017-09-24 00:13:34] [applet-rx] found 631 addresses at 199.255.40.174 for ut.
[2017-09-24 01:13:34] [applet-rx] found 637 addresses at 199.255.40.174 for ut.
[2017-09-24 02:13:34] [applet-rx] found 636 addresses at 199.255.40.174 for ut.
[2017-09-24 03:13:34] [applet-rx] found 640 addresses at 199.255.40.174 for ut.
[2017-09-24 04:13:34] [applet-rx] found 640 addresses at 199.255.40.174 for ut.
[2017-09-24 05:13:32] [refused] on 199.255.40.174:28900.
[2017-09-24 06:13:22] [refused] on 199.255.40.174:28900.
[2017-09-24 07:13:22] [refused] on 199.255.40.174:28900.
[2017-09-24 08:13:22] [refused] on 199.255.40.174:28900.
[2017-09-24 09:13:22] [refused] on 199.255.40.174:28900.
[2017-09-24 10:13:22] [refused] on 199.255.40.174:28900.
[2017-09-24 11:13:22] [refused] on 199.255.40.174:28900.
[2017-09-24 12:13:22] [refused] on 199.255.40.174:28900.
[2017-09-24 13:13:22] [refused] on 199.255.40.174:28900.
[2017-09-24 14:13:22] [refused] on 199.255.40.174:28900.
[2017-09-24 15:13:22] [refused] on 199.255.40.174:28900.
[2017-09-24 16:13:22] [refused] on 199.255.40.174:28900.
[2017-09-24 17:13:22] [refused] on 199.255.40.174:28900.
This comes as no surprise.
This happened last year (and picture below)
This happened the year before
And now it happened this year.
What happens next? If empirical data is reliable, the masterserver should be online shortly and accepting connections again soon as in the figure below.
In the meanwhile, consider migrating to one of the 333networks masterservers.
Psst! We have a new version coming soon!