Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is the GovInfo API down? #34

Closed
jose-pvargas opened this issue Mar 28, 2019 · 3 comments
Closed

Is the GovInfo API down? #34

jose-pvargas opened this issue Mar 28, 2019 · 3 comments

Comments

@jose-pvargas
Copy link

I am unable to get to the documentation page for GovInfo's API. The connection times out with a message of "api.govinfo.gov’s server IP address could not be found." Tried connecting with a Mac and Windows machine through Google Chrome.

Following the example for the Congressional Record collection found here, https://www.govinfo.gov/features/api, fails for the same reason. Attempted the example with both Python's requests and cURL but no success.

Is the API down?

Here is the error from Python's requests.

requests.exceptions.ConnectionError: HTTPSConnectionPool(host='api.govinfo.gov', port=443): Max retries exceeded with url: /collections/CREC/2018-10-01T00:00:00Z?pageSize=10&offset=0
(Caused by NewConnectionError('<requests.packages.urllib3.connection.VerifiedHTTPSConnection object at 0x110a79650>: Failed to establish a new connection: [Errno 8] nodename nor servname provided, or not known',))

Attempted passing the api.data.gov API key as an HTTP query and as a query parameter.

@jonquandt
Copy link
Member

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

@jose-pvargas
Copy link
Author

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?

@jonquandt
Copy link
Member

jonquandt commented Mar 28, 2019

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants