Is the GovInfo API down? about api HOT 3 CLOSED

Is this an issue for you right now?

We had an issue earlier this morning, but it was resolved and service was restored around 10am Eastern.

I am able to get reaponses both internally and externally. For example,

https://api.govinfo.gov/collections?api_key=DEMO_KEY

is returning the expected collection list.

The first CREC example is also returning for me.

{"count":4427,"message":null,"nextPage":"https://api.govinfo.gov/collections/CREC/2018-10-01T00:00:00Z?offset=10&pageSize=10","previousPage":null,"packages":[{"packageId":"CREC-2018-12-13","lastModified":"2019-03-28T14:13:47Z","packageLink":"https://api.govinfo.gov/packages/CREC-2018-12-13/summary","docClass":"CREC","title":"Congressional Record Volume 164, Issue 197, (December 13, 2018)","congress":"115"},{"packageId":"CREC-2018-12-21","lastModified":"2019-03-28T12:54:33Z","packageLink":"https://api.govinfo.gov/packages/CREC-2018-12-21/summary","docClass":"CREC","title":"Congressional Record Volume 164, Issue 202, (December 21, 2018)","congress":"115"},{"packageId":"CREC-2018-12-27","lastModified":"2019-03-28T12:49:16Z","packageLink":"https://api.govinfo.gov/packages/CREC-2018-12-27/summary","docClass":"CREC","title":"Congressional Record Volume 164, Issue 205, (December 27, 2018)","congress":"115"},{"packageId":"CREC-2018-12-17","lastModified":"2019-03-28T12:48:30Z","packageLink":"https://api.govinfo.gov/packages/CREC-2018-12-17/summary","docClass":"CREC","title":"Congressional Record Volume 164, Issue 198, (December 17, 2018)","congress":"115"},{"packageId":"CREC-2018-12-20","lastModified":"2019-03-28T12:46:05Z","packageLink":"https://api.govinfo.gov/packages/CREC-2018-12-20/summary","docClass":"CREC","title":"Congressional Record Volume 164, Issue 201, (December 20, 2018)","congress":"115"},{"packageId":"CREC-2018-12-12","lastModified":"2019-03-28T12:36:52Z","packageLink":"https://api.govinfo.gov/packages/CREC-2018-12-12/summary","docClass":"CREC","title":"Congressional Record Volume 164, Issue 196, (December 12, 2018)","congress":"115"},{"packageId":"CREC-2018-12-24","lastModified":"2019-03-28T12:36:48Z","packageLink":"https://api.govinfo.gov/packages/CREC-2018-12-24/summary","docClass":"CREC","title":"Congressional Record Volume 164, Issue 204, (December 24, 2018)","congress":"115"},{"packageId":"CREC-2018-12-11","lastModified":"2019-03-28T12:31:54Z","packageLink":"https://api.govinfo.gov/packages/CREC-2018-12-11/summary","docClass":"CREC","title":"Congressional Record Volume 164, Issue 195, (December 11, 2018)","congress":"115"},{"packageId":"CREC-2018-12-19","lastModified":"2019-03-28T12:27:00Z","packageLink":"https://api.govinfo.gov/packages/CREC-2018-12-19/summary","docClass":"CREC","title":"Congressional Record Volume 164, Issue 200, (December 19, 2018)","congress":"115"},{"packageId":"CREC-2019-03-27","lastModified":"2019-03-28T10:33:07Z","packageLink":"https://api.govinfo.gov/packages/CREC-2019-03-27/summary","docClass":"CREC","title":"Congressional Record Volume 165, Issue 53, (March 27, 2019)","congress":"116"}]}

Will investigate to see if we're seeing any access errors though

from api.

Thank you for the quick response @jonquandt. It currently is an issue for me. I retried the CREC example but still receive the failed DNS lookup message in my original post. Are you able to view the https://api.govinfo.gov/docs page?

from api.

Yes, I am, on multiple devices

The prior issue was related to moving some internal name resolution around, so please try to clear your DNS cache using ipconfig /flushdns on windows.

Not an ideal answer, but I'm hopeful that will solve the issue.

from api.