ezidstatus

Information about May 21st outage

ezidstatus — Wed, 22 May 2013 16:16:39 +0000

The outage affecting EZID service yesterday was part of a CDL-wide outage. In other words, all CDL services hosted in our organization’s data center were unavailable during this time (from 3:00 pm to 4:10 pm Pacific). The root cause is not known at this time. The data center staff are currently working on determine the cause.

We apologize for this inconvenience, and we will provide you with further information when it is available.

Network outage over

ezidstatus — Tue, 21 May 2013 23:18:24 +0000

The network outage appears to be over. All systems are accessible again.

Network outage

ezidstatus — Tue, 21 May 2013 22:12:19 +0000

CDL appears to be suffering some type of network outage. All services are inaccessible, including EZID and ARK identifier resolution.

Metadata problem resolved

ezidstatus — Tue, 21 May 2013 13:20:40 +0000

DataCite has resolved the problem. DOIs can be created and updated again.

DOI metadata problems

ezidstatus — Tue, 21 May 2013 00:21:28 +0000

EZID has just begun encountering a problem in which DataCite XML metadata records that have always been accepted by DataCite are now being rejected by DataCite with the error,

“[xml] xml error: s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than ‘xs:appinfo’ and ‘xs:documentation’. Saw ’301 Moved Permanently’.”

Although DOI resolution is not affected, you may be unable to create or update DOIs while this problem persists.

We have contacted DataCite technical support, and hopefully the problem will be resolved shortly.

Brief network outage

ezidstatus — Tue, 14 May 2013 19:52:41 +0000

CDL recently experienced a network outage lasting approximately 15 minutes. All appears fine now.

DataCite is up

ezidstatus — Tue, 16 Apr 2013 12:10:26 +0000

DataCite is up again.

DataCite MDS is down

ezidstatus — Mon, 15 Apr 2013 18:31:15 +0000

The DataCite metadata server is down. DOI registrations and updates will not be possible until it is up again. Identifier resolutions are not affected.

EZID denial of service problem

ezidstatus — Mon, 15 Apr 2013 18:29:04 +0000

For approximately 45 minutes this morning EZID was extremely slow to the point of being non-responsive. The reason is that an EZID customer was issuing a large number of simultaneous requests, which had the effect of creating a denial-of-service condition. EZID is again functioning normally. We will be working with the customer to define a more supportable workload.

Brief outage Sunday evening

ezidstatus — Sun, 03 Mar 2013 07:54:38 +0000

To perform an internal switchover, EZID will be offline for approximately one minute during tomorrow (Sunday) night’s regular maintenance window (8-9pm Pacific time).