Recent Updates Page 2 Toggle Comment Threads | Keyboard Shortcuts

  • ezidstatus 2:15 pm on February 9, 2018 Permalink  

    Excessive usage encountered 

    EZID suffered a brief interruption when it was restarted to ban a particular user.  We’re unsure whether the user was malicious, or just being over-enthusiastic in their stress testing.

  • ezidstatus 11:02 am on January 18, 2018 Permalink  

    N2T resolver backlog 

    Due to heavy activity, there is a backlog in registering ARK identifiers with the N2T resolver.  The backlog should clear in about a day.

  • ezidstatus 3:07 pm on January 16, 2018 Permalink  

    The backlog has cleared. DOI registrations will be reflected in the Handle System with their normal delay, a few seconds to a few minutes.

  • ezidstatus 9:31 am on January 16, 2018 Permalink  

    There is a backlog in DOI registrations, which will be finished in about 4 hours. (Written at 09:30 PST) 

  • ezidstatus 9:20 am on April 2, 2017 Permalink  

    Database upgrade completed 

    The database upgrade ended up taking about 60min, but is completed.

  • ezidstatus 7:36 am on April 2, 2017 Permalink  

    Database upgrade 

    During this morning’s maintenance window we’re going to be upgrading EZID’s database.  Based on upgrades of similar systems, we expect EZID to be down for approximately 20 minutes.

  • ezidstatus 9:11 am on January 24, 2017 Permalink  

    Higher-than-normal DOI activity 

    EZID is encountering higher-than-normal DOI activity.  It may take up to a day for a newly-registered DOI to appear in the Handle System.  We expect the activity to subside within the next couple days.  In the meantime, we’re working with DataCite to see if there’s a way we can push requests through faster.

  • ezidstatus 8:44 pm on January 11, 2017 Permalink  

    N2T problem resolved 

    The N2T database problem has been resolved and EZID and N2T are again connected.  New ARK identifiers will resolve.  ARK identifiers created during the outage are being back-registered into N2T now; that process will complete in about 4 hours.

  • ezidstatus 7:22 am on January 9, 2017 Permalink  

    N2T binder/resolver down 

    At 9:34pm PDT last night the N2T binder/resolver suffered a database failure.  At 7:00am PDT this morning EZID was temporarily disconnected from N2T, meaning that EZID identifier operations will now succeed normally, with no further internal server errors.  The only effect is that newly-registered ARK identifiers will not resolve.  When N2T is back online, any ARK identifiers created during the outage will automatically be registered with N2T.  DOI identifiers are unaffected.

  • ezidstatus 2:18 pm on November 8, 2016 Permalink  

    Intermittent errors noticed, addressed 

    An identifier subsystem that EZID talks to has been returning intermittent errors for the last day or so, which to EZID clients look like internal server errors.  Because these errors are intermittent, we’ve added some extra retry logic in EZID to shield EZID users from them.  In the meantime, we’re continuing to investigate the problems with the subsystem.

Compose new post
Next post/Next comment
Previous post/Previous comment
Show/Hide comments
Go to top
Go to login
Show/Hide help
shift + esc