DJ Event Planner (DJEP) | Server Status Page

 

Current Status: No known issues.

Current Status: There are currently issues with the DJ Event Planner servers.

RESOLVEDIssue: Server 26 Unresponsive
Date: February 25th 2021


Time: 12:55 pm Central Time

We are currently experiencing an issue that is affecting server number 26. All other servers are unaffected.
A ticket was submitted to the data center and we are awaiting their reply.


Time: 1:13 pm Central Time

The server was rebooted and is now back online. Issue is now resolved.


RESOLVEDIssue: Data Center Power Loss
Date: January 30th 2021




Technical Difficulties

Dear DJ Event Planner User,

This describes the outagae that occurred on January 30, 2021.

This issue was brought to our attention at 12:05 pm CST. After a brief investigation it was brought to our attention that the issue was coming from our Data Center. We immediately put in a ticket with Our Data Center requesting further information. We also created a FaceBook post on our DJ Event Planner Page and also within the DJEP User to User Group to notify our users of the issue.

By 1:30 pm CST we were informed that the cause of the issue was due to a power outage at the data center and that they were working to restore power. Power was restored by 1:54 pm CST. All DJEP accounts were once again back online.

We understand that you may have attempted to access your DJEP account during this outage and were greeted with an "unable to acess" message. We apologies for the inconvenience and thank you for your patience and understanding. Outages lasting longer than 15 minutes are few and far between, the last of which was approximately 8 years ago at which time this too was monitored and handled by the support team.

Once again, we apologies for any inconvenience and appreciate your patience.

The DJ Event Planner Staff Members
Troy, Charlene, Alex, Milissa, and Fletcher

There was a known issue with the DJ Event Planner servers.

March 18th 2019 - 5:55am Central Time

We are currently experiencing a network routing issue at the data center. This issue is affecting servers 21-29. All other servers are unaffected.


A ticket was submitted to the data center and we will be in contact with them in the next hour.


For those affected the behaviour is slow load times for the web pages.

RESOLVED

July 18th 201 - 12:55pm Central Time (6:55 GMT)

It appears there is an issue at the data center

We have submitted a ticket to the data center at 12:55pm and we are expecting a response shortly.

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

Their response from 1:05 PM Central: We aware of an issue impacting some of our customers. Full details are not available at this point, however we will provide an RFO as soon as possible. We ask for your understanding and patience as we assess and resolve this situation.

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

Update as of 1:18 pm. No response from the data center yet. We will be calling them if no response in the next 10 minutes. Our apologies for the issue, but it is beyond our control at this point. We unfortunately do not have an estimated time as to when the servers will be reachable again.

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

Update as of 1:25 pm. All servers are now reachable. It appears the data center has resolved the issue. We will follow up with them regarding this issue.



Issue with Server 5 (Potentially resolved)

July 27th 2017 - 11:10am Central Time (17:10 GMT)

We are currently experiencing an intermitent connection issue with Server 5.
The server is connecting, then disconnecting within a few minutes, then reconnecting a few minutes after that, on a repeated cycle. We are researching and attempting to repair the issue as quickly as possible.

Once we know more about the intermitent connection issue, we will update this page.

July 27th 2017 - 11:44am Central Time (17:44 GMT)

We are working towards trying to reboot the server using a KVM, however this is currently not working as expected. We will continue to attempt to connect and repair the issue.

We are also working on a contingency plan, where we are moving all users from Server 5 to the new Server 23. We will be restoring all data from the daily backups, taken this morning at 4am. If we are unable to restore server 5, we will look at switching everyone over automatically,

Users will not have to do change anything as we will deal with all DNS and movement tasks here.

July 27th 2017 - 12:13pm Central Time (18:13 GMT)

It appears we have been able to get server 5 working and staying connected. We will continue to moniter the situation, before we make any final decisions on moving everyone to a different server.



URGENT UPDATE ----- July 27th 2017 - 2:22pm Central Time (20:22 GMT)


IMPORTANT INFORMATION - Unfortunately we've been unable to restore Server 5 which means our backup plan is in motion. We will be moving everyones accounts from server 5 to the new server ( Number 23 ). This will take the team approxiamtely one hour to do, after which a DNS update will be done to move the domains. This DNS update should only take a couple of hours to propagate, but you should allow upto 12-24 hours.


All data entered up until 12:00 noon Central Time ( 12:00pm GMT ) will be restored. Any data entered since then will not be available and will need to be re-entered. We apologize for the inconvenience this will cause.


Once the domains have been moved and DNS updated, we will update this page accordingly


Important DNS Information: If you updated your DNS using IP addresses instead of nameservers ( such as users on a subdomain standalone ie: clients.domainname.com ) you will need to update your DNS records accordingly. We will deal with this on a case by case basis via the official support forum ( http://www.eventplannerforum.com )

Please See: Official Forum Post



July 27th 2017 - 5:00pm Central Time (23:00 GMT) - ISSUE RESOLVED


Due to a hardware failure on a server your DJ Event Planner account was on, we have moved your account to a new server.


Today at approximately 11:00am Central Time (5pm GMT), Server Number 5 started failing. We attempted to repair the server and determine what the problem was and tried to resolve it. We were unsuccesful.


Before it failed completely, we are able to run the daily backup. We migrated the data backup from the offsite storage location to the new server. The backup occured around 12:20pm Central Time. (6:20 GMT). For much of the afternoon the server was unavailable. Any data you entered during that time will need to be re-entered.


The new server is faster, more secure, and is a more stable environment. We have deployed the latest hardware and software on the new servers. We will continue to employee the same daily offsite backup solution, which in this case worked flawlessly.


We made some backend changes which allow the sites to come back up in relatively short order. We were able to update the DNS Host Entries, which employs IP redirection. It may take up to 24 hours for these changes to propagate. However, it usually occurs much more quickly.


You may notice some downtime while this propagation occurs. We apologize for the inconvenience this may cause.


Because of this move, we would suggest updating your standalone domains DNS records.


If you're using nameservers such as "ns1.controlhelm5.com", you will need to change these to:
ns1.controlhelm23.com
ns2.controlhelm23.com


If you're using a IP numbers instead you will need to update your records to the following IP address:
66.180.33.205


You should update these as soon as possible to speed up the propagation of the new DNS.


If you have any questions, please post on the official support forum (http://eventplannerforum.com)


Again, apologies for the issue, but as you know, sometimes equipment breaks. Due to the hard work of my staff, we were able to recover quickly.


Troy Ackerman

DJ Event Planner