Re: [PDB Tech] PeeringDB API Discrepency

On Tue, 4 Oct 2016, Arnold Nipper wrote: > On 04.10.2016 18:53, James Bensley wrote: > > On 13 September 2016 at 11:00, Stefan Pratter wrote: > >> Hi, > >> > >> Thank you for bringing this to our attention, i have opened a github ticket > >> for it here: > >> > >>

Re: [PDB Tech] PeeringDB API Discrepency

wrote: > Agreed, not sure how that got in, made > https://github.com/peeringdb/peeringdb/issues/71 and will check it out / > add better tests. > > > On Oct 4, 2016 3:46 PM, "Arnold Nipper" <arnold.nip...@de-cix.net> wrote: > On 04.10.2016 22:29, Chris Caput

Re: [PDB Tech] allow empty IP field or not?

Sometimes folks have the IPv6 flag enabled, but they aren't yet doing IPv6 at a particular IXP. If they fill out the IPv6 address, we've seen participants with automated session configuration based on PeeringDB try to ND for a router that isn't yet configured to handle the ND. This results

Re: [PDB Tech] peeringDB Python Module Issues with Python 3?

Same here: https://github.com/peeringdb/django-peeringdb/issues/37 "errors with django 3 so limit to django 2 or fix them #37" Bill, if your issue is unique after review of: https://github.com/peeringdb/django-peeringdb/issues consider a new issue with details. The django 3 issue

Re: [PDB Tech] Problem doing initial 'peeringdb sync', foreign key constraint fails?

Hi. Does restarting with a fresh/empty local database help at all? Also, what does the following show?: peeringdb --version django-admin --version pip freeze Thanks, Chris On Fri, 15 May 2020, Brian Dickson wrote: > Arnold Nipper said to send to this list. > > (This is kind of urgent for me,

Re: [PDB Tech] Problem doing initial 'peeringdb sync', foreign key constraint fails?

6/lib/python3.6/asyncio/base_events.py", > line 488, in run_until_complete > >     return future.result() > >   File > "/Users/bdickson1/Documents/projects/site-selection/pdbvenv/lib/python3.6/site-packages/peeringdb/_tasks_async.py", > line 41, in _wr

[PDB Tech] PeeringDB development container

For people wanting to contribute code to PeeringDB, I think this week is a big deal. In case you missed the social media, check out: https://docs.peeringdb.com/blog/contributing_code/ https://github.com/peeringdb/peeringdb/blob/master/docs/container.md That later link contains step by

Re: [PDB Tech] new rate limiting mechanism is too strict

All, I am behind the throttling rollout in the last 24 hours, and have worked with Theo to loosen things up for now. I've also reached out to pierky re changes requested for arouteserver and will endeavor to delay resumption of the same throttling until after arouteserver users have had

Re: [PDB Tech] new rate limiting mechanism is too strict

On Tue, 17 May 2022, Arnold Nipper wrote: > On 17.05.2022 18:54, Chris Caputo wrote: > > Highlights for all client developers: > > I would add: instead of querying PDB for each ASN one by one, use the > asn__in=$list_of_ASN_separated_by_commata feature. Ooh 200 IQ mane

[PDB Tech] PeeringDB API throttling status and schedule

After the initial introduction of PeeringDB API throttling, some software both open source and private, has been identified and updated. (open source details are below; please upgrade and encourage others to do so) This API throttling is being implemented to control costs by encouraging

[PDB Tech] PeerFinder support for API keys

Hi all, For those using PeerFinder, I have submitted a PR to add support for API keys: https://github.com/rucarrol/PeerFinder/pull/17 Feel free to pull from my fork if you need support immediately: https://github.com/ccaputo/PeerFinder Happy to answer questions about this. Thanks, Chris

Re: [PDB Tech] PeeringDB API throttling status and schedule

L, other > dependencies, and bugging the original peeringDB-source. > > BR Jörg > > On 31 May 2022, at 21:31, Chris Caputo wrote: > > > After the initial introduction of PeeringDB API throttling, some software > > both open source and private, has been identifi

Re: [PDB Tech] PeeringDB API throttling status and schedule

you, Chris On Tue, 31 May 2022, Chris Caputo wrote: > After the initial introduction of PeeringDB API throttling, some software > both open source and private, has been identified and updated. (open > source details are below; please upgrade and encourage others to do so) > > This

Re: [PDB Tech] PeeringDB API throttling status and schedule

you, Chris On Tue, 31 May 2022, Chris Caputo wrote: > After the initial introduction of PeeringDB API throttling, some software > both open source and private, has been identified and updated. (open > source details are below; please upgrade and encourage others to do so) > > This

Re: [PDB Tech] PeeringDB API throttling status and schedule

you, Chris On Tue, 31 May 2022, Chris Caputo wrote: > After the initial introduction of PeeringDB API throttling, some software > both open source and private, has been identified and updated. (open > source details are below; please upgrade and encourage others to do so) > > This

Re: [PDB Tech] PeerFinder support for API keys

Hi. Just a quick note to say the below was merged into PeerFinder a few days ago. Chris On Mon, 23 May 2022, Chris Caputo wrote: > Hi all, > > For those using PeerFinder, I have submitted a PR to add support for API > keys: > > https://github.com/rucarrol/PeerFinder/pull

Re: [PDB Tech] PeeringDB API throttling status and schedule

you, Chris On Tue, 31 May 2022, Chris Caputo wrote: > After the initial introduction of PeeringDB API throttling, some software > both open source and private, has been identified and updated. (open > source details are below; please upgrade and encourage others to do so) > > This

Re: [PDB Tech] PeeringDB API throttling status and schedule

you, Chris On Tue, 31 May 2022, Chris Caputo wrote: > After the initial introduction of PeeringDB API throttling, some software > both open source and private, has been identified and updated. (open > source details are below; please upgrade and encourage others to do so) > > This

Re: [PDB Tech] PeeringDB API throttling status and schedule

, Chris On Mon, 15 Aug 2022, Chris Caputo wrote: > Per the below plan, this change was just implemented: > > --- > On August 15th, adjust and watch for feedback from the community: > > - anonymous queries limited to 10/minute per IP address > - authenticated queries lim

[PDB Tech] peeringdb-py example setup

In case useful to others, below is how peeringdb-py is set up & upgraded at the SeattleIX. Questions/improvements welcome. Chris --- INSTALL: mkdir ~/peeringdb-py && cd ~/peeringdb-py virtualenv --python=python3 pdbvenv source pdbvenv/bin/activate pip install --upgrade pip pip install -U

Re: [PDB Tech] PeeringDB Account Verification

As I understand things, an account is needed in order to create/use an API key. Noelle, please be aware of: https://github.com/peeringdb/peeringdb/issues/380 The apparent intention of that issue is that accounts without an organization affiliation will eventually be purged. You may want to

Re: [PDB Tech] PeeringDB API throttling status and schedule

. Thank you, Chris On Sun, 14 Aug 2022, Chris Caputo wrote: > Sorry - I totally jumped the gun on what UTC day it is! Reverted back to > the August 8th settings: > > - anonymous queries limited to 20/minute per IP address > - authenticated queries limited to 60/minute per user

Re: [PDB Tech] PeeringDB API throttling status and schedule

Sorry - I totally jumped the gun on what UTC day it is! Reverted back to the August 8th settings: - anonymous queries limited to 20/minute per IP address - authenticated queries limited to 60/minute per user/org Chris On Sun, 14 Aug 2022, Chris Caputo wrote: > Per the below p

Re: [PDB Tech] PeeringDB API throttling status and schedule

you, Chris On Tue, 31 May 2022, Chris Caputo wrote: > After the initial introduction of PeeringDB API throttling, some software > both open source and private, has been identified and updated. (open > source details are below; please upgrade and encourage others to do so) > > This

Re: [PDB Tech] PeeringDB API throttling status and schedule (fwd)

you, Chris On Tue, 31 May 2022, Chris Caputo wrote: > After the initial introduction of PeeringDB API throttling, some software > both open source and private, has been identified and updated. (open > source details are below; please upgrade and encourage others to do so) > > This

Re: [PDB Tech] PeeringDB API throttling status and schedule

less conditions & feedback warrant otherwise. Thanks, Chris On Mon, 8 Aug 2022, Chris Caputo wrote: > Per the below plan, this change was just implemented: > > --- > On August 8th, adjust and watch for feedback from the community: > > - anonymous queries limited t

Re: [PDB Tech] PeeringDB API throttling status and schedule

. Thank you, Chris On Tue, 31 May 2022, Chris Caputo wrote: > After the initial introduction of PeeringDB API throttling, some software > both open source and private, has been identified and updated. (open > source details are below; please upgrade and encourage others to do so) >

Re: [PDB Tech] PeeringDB API throttling status and schedule (fwd)

service vs an invalid api key quietly lumped into > > the anonymous rate-limit bucket. > > This is something we should fix. I've filed > https://github.com/peeringdb/peeringdb/issues/1220 to get it addressed > > -Steve > > > > > > On Aug 9, 2022, at 1

[PDB Tech] non-canonical queries losing auth on redirect to canonical

It is important to query against the canonical "www.peeringdb.com". Python and presumably other libraries will drop the authentication request header on a redirect, as a safety precaution: https://github.com/psf/requests/blob/177dd90f/requests/sessions.py#L284-L296 Unfortunately, when this

Re: [PDB Tech] Question about API ratelimits

On Thu, 11 Apr 2024, Tom Strickx wrote: > Hey folks, > > We're wondering how the ratelimits are enforced these days. > Specifically, authenticated (so with API key) requests. Are these enforced > by API-key, by AccountID, by IP, by subnet, by star sign, ...? > Let me know if there's some piece of