Duration in Open Events stream

[Vijay Sharma]

Hey,

I'm building an app around the Meetup API.  I can mostly manage with just the Open Events stream (http://www.meetup.com/meetup_api/docs/stream/2/open_events/), however it doesn't have the "duration" field, which means I would have to hit the API with another call.  

Making a secondary call to the API to get the duration field for each meetup would take us over the 200 calls per hour (more than 200 events per hour can come down via the stream).  The only field I need from the secondary call is "duration"; is there any way of getting this field via the stream, or raising the limit so that we can get the "duration" field for all meetups?

Thanks

[Doug Tangren]

This is definitely doable. I'll open a ticket to add this

 

Thanks

--
--
You received this message because you are subscribed to the Google
Groups "Meetup API" group.
To unsubscribe from this group, send email to
meetup-api+...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/meetup-api?hl=en?hl=en

---
You received this message because you are subscribed to the Google Groups "Meetup API" group.
To unsubscribe from this group and stop receiving emails from it, send an email to meetup-api+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Vijay Sharma]

Hey Doug,

I was wondering if we could get the category in there too?  Also, could I be cheeky and ask for an ETA?  :-)

Thanks again!

Vijay

[Doug Tangren]

On Tue, May 6, 2014 at 6:47 PM, Vijay Sharma <wij...@gmail.com> wrote:

Hey Doug,

I was wondering if we could get the category in there too?  Also, could I be cheeky and ask for an ETA?  :-)

It's in our ticketing system now. I'm a little tied up at the moment so I wouldn't expect it for a few weeks.

[Doug Tangren]

On Wed, May 7, 2014 at 10:04 AM, Doug Tangren <do...@meetup.com> wrote:

On Tue, May 6, 2014 at 6:47 PM, Vijay Sharma <wij...@gmail.com> wrote:

Hey Doug,

I was wondering if we could get the category in there too?  Also, could I be cheeky and ask for an ETA?  :-)

It's in our ticketing system now. I'm a little tied up at the moment so I wouldn't expect it for a few weeks.

You should now be able to find an event's duration ( if an end time is set ) and group category in the response of the 2/open_events api stream -- http://www.meetup.com/meetup_api/docs/stream/2/open_events/#response

[salt...@gmail.com]

According to my log files the meetup servers have been timing out starting 2014-05-27 17:26:40 and are still doing so. Requests made to the API from my server are consistently returning:

Failed to connect to api.meetup.com port 443: Connection timed out accessing https://api.meetup.com/2/event/182956152?fields=rsvp_rules&only=description%2Cid%2Cevent_url%2Cgroup.id%2Cgroup.name%2Cgroup.who%2Cid%2Cname%2Crsvp_rules.guest_limit%2Cstatus%2Ctime%2Cyes_rsvp_count&access_token=xyz

Using the console does not have this problem and accessing the server from another machine on my end does not have this problem. I created a test script which basically just does a TCP connect (via PHP) to the api.meetup.com IP on port 443 and this script runs fine on my machine but does not connect on my server. Is it possible my specific server (which has been accessing Meetup fine for a couple of years) is now being “blocked” by Meetup in some way?

Dominique Lacerte

[Vijay Sharma]

Doug,

You are a star! :)

Thank you so much for taking the time to help us out with this.  Hopefully you will like how Meetups are used within our app, we launch in the next week, so I'll shoot you a mail for you to take a look at exactly what you hard work helped us achieve! 

Thanks again,

Vijay

[salt...@gmail.com]

My ISP has discovered that the meetup IP was blacklisted and this was preventing the connections. I don’t know what meetup has been up to in order to get blacklisted. 😉 Things seem better now. 😊

Dominique

[Doug Tangren]

On Fri, May 30, 2014 at 3:02 AM, <salt...@gmail.com> wrote:

My ISP has discovered that the meetup IP was blacklisted and this was preventing the connections. I don’t know what meetup has been up to in order to get blacklisted. 😉 Things seem better now. 😊

Thanks Dominique. I'll let our systems team know.

 

Dominique

From: salt...@gmail.com
Sent: ‎Wednesday‎, ‎28‎ ‎May‎, ‎2014 ‎7‎:‎14‎ ‎AM
To: meetup-api

According to my log files the meetup servers have been timing out starting 2014-05-27 17:26:40 and are still doing so. Requests made to the API from my server are consistently returning:

Failed to connect to api.meetup.com port 443: Connection timed out accessing https://api.meetup.com/2/event/182956152?fields=rsvp_rules&only=description%2Cid%2Cevent_url%2Cgroup.id%2Cgroup.name%2Cgroup.who%2Cid%2Cname%2Crsvp_rules.guest_limit%2Cstatus%2Ctime%2Cyes_rsvp_count&access_token=xyz

Using the console does not have this problem and accessing the server from another machine on my end does not have this problem. I created a test script which basically just does a TCP connect (via PHP) to the api.meetup.com IP on port 443 and this script runs fine on my machine but does not connect on my server. Is it possible my specific server (which has been accessing Meetup fine for a couple of years) is now being “blocked” by Meetup in some way?

Dominique Lacerte

[Doug Tangren]

On Thu, May 29, 2014 at 10:52 AM, Vijay Sharma <wij...@gmail.com> wrote:

Doug,

You are a star! :)

Thank you so much for taking the time to help us out with this.  Hopefully you will like how Meetups are used within our app, we launch in the next week, so I'll shoot you a mail for you to take a look at exactly what you hard work helped us achieve! 

Thank you for the kind words Vijay. Would you be able to share what kind of app you are building? We are always interested in seeing what people are doing with the Meetup platform.

[salt...@gmail.com]

Hi,

My Meetup API script has been running for over a year and I’ve noticed recently that it has gotten very slow, so much so that it is unusable a majority of the time. I did some investigation and it appears that sometimes the requests for data from the Meetup API are taking very long, approximately 30 seconds each. Is there some rate limiting that was introduced that is causing this? Here is a sample of the times for various URLs:

2014-06-01 02:14:12 ERROR: Duration of https://api.meetup.com/2/profile/1993281/8134674?fields=role%2Cstatus&only=role%2Cstatus&access_token=XYZ: 30.174s

2014-06-01 02:14:42 ERROR: Duration of https://api.meetup.com/2/profile/1993281/8134674?fields=role%2Cstatus&only=role%2Cstatus&access_token=XYZ: 30.165s

2014-06-01 02:15:12 ERROR: Duration of https://api.meetup.com/2/event/185824662?fields=self&only=group.id%2Cgroup.name%2Cgroup.urlname%2Cid%2Cname%2Cstatus%2Ctime%2Cself.actions%2Cself.rsvp&access_token=XYZ: 30.182s

2014-06-01 02:15:42 ERROR: Duration of https://api.meetup.com/2/events?member_id=self&status=upcoming&time=1402102800000%2C1402117200000&fields=rsvp_rules%2Cself&only=group.id%2Cgroup.name%2Cgroup.urlname%2Cid%2Cname%2Crsvp_rules.guest_limit%2Cstatus%2Ctime%2Cself.actions%2Cself.rsvp&page=300&offset=0&access_token=XYZ: 30.203s

2014-06-01 02:16:13 ERROR: Duration of https://api.meetup.com/2/profiles?group_id=1993281&only=member_id%2Cname%2Crole&status=active&member_id=8134674&page=300&offset=0&access_token=XYZ: 30.192s

2014-06-01 02:16:43 ERROR: Duration of https://api.meetup.com/2/profiles?group_id=3707622&only=member_id%2Cname%2Crole&status=active&member_id=8134674&page=300&offset=0&access_token=XYZ: 30.296s

2014-06-01 02:17:13 ERROR: Duration of https://api.meetup.com/2/profiles?group_id=3743392&only=member_id%2Cname%2Crole&status=active&member_id=8134674&page=300&offset=0&access_token=XYZ: 30.173s

Dominique

[Doug Tangren]

On Sun, Jun 1, 2014 at 5:15 AM, <salt...@gmail.com> wrote:

Hi,

My Meetup API script has been running for over a year and I’ve noticed recently that it has gotten very slow, so much so that it is unusable a majority of the time. I did some investigation and it appears that sometimes the requests for data from the Meetup API are taking very long, approximately 30 seconds each. Is there some rate limiting that was introduced that is causing this? Here is a sample of the times for various URLs:

2014-06-01 02:14:12 ERROR: Duration of https://api.meetup.com/2/profile/1993281/8134674?fields=role%2Cstatus&only=role%2Cstatus&access_token=XYZ: 30.174s

Do these timings directly reflect the time from request to response without other factors like retried attempts? 

Requests opting for extra fields can result in somewhat slower response times due to additional resource usage to fetch the extra data but 30 is definitely not an expected latency. Below is an example of the same request using a masked, but valid, oauth2 token. 

time curl "https://api.meetup.com/2/profile/1993281/8134674?fields=role%2Cstatus&only=role%2Cstatus&access_token=..."

{"status":"active","role":"Organizer"}

real 0m0.207s

user 0m0.011s

sys 0m0.008s

I will have a closer look into this when I get into the office on Monday but in the meantime, can post back with a few things if they are available.

Each response includes a header called "X-Meetup-server". We serve API requests from a group of dedicated servers. The X-Meetup-server header indicates the name of a specific server within that group. 

For instance the following request indicates is was served by the server named "api13.int.meetup.com".

time curl -i "https://api.meetup.com/2/profile/1993281/8134674?fields=role%2Cstatus&only=role%2Cstatus&access_token=..." 2>/dev/null | grep "X-Meetup-server"

X-Meetup-server: api13.int.meetup.com

real 0m0.220s

user 0m0.010s

sys 0m0.008s

If you are able to, for these long response times, can you see if there is any consistency in the the X-Meetup-server returned. 

I will look into if anything peculiar happened around the time of these requests.

 

2014-06-01 02:14:42 ERROR: Duration of https://api.meetup.com/2/profile/1993281/8134674?fields=role%2Cstatus&only=role%2Cstatus&access_token=XYZ: 30.165s

2014-06-01 02:15:12 ERROR: Duration of https://api.meetup.com/2/event/185824662?fields=self&only=group.id%2Cgroup.name%2Cgroup.urlname%2Cid%2Cname%2Cstatus%2Ctime%2Cself.actions%2Cself.rsvp&access_token=XYZ: 30.182s

2014-06-01 02:15:42 ERROR: Duration of https://api.meetup.com/2/events?member_id=self&status=upcoming&time=1402102800000%2C1402117200000&fields=rsvp_rules%2Cself&only=group.id%2Cgroup.name%2Cgroup.urlname%2Cid%2Cname%2Crsvp_rules.guest_limit%2Cstatus%2Ctime%2Cself.actions%2Cself.rsvp&page=300&offset=0&access_token=XYZ: 30.203s

2014-06-01 02:16:13 ERROR: Duration of https://api.meetup.com/2/profiles?group_id=1993281&only=member_id%2Cname%2Crole&status=active&member_id=8134674&page=300&offset=0&access_token=XYZ: 30.192s

2014-06-01 02:16:43 ERROR: Duration of https://api.meetup.com/2/profiles?group_id=3707622&only=member_id%2Cname%2Crole&status=active&member_id=8134674&page=300&offset=0&access_token=XYZ: 30.296s

2014-06-01 02:17:13 ERROR: Duration of https://api.meetup.com/2/profiles?group_id=3743392&only=member_id%2Cname%2Crole&status=active&member_id=8134674&page=300&offset=0&access_token=XYZ: 30.173s

Dominique

--

[Doug Tangren]

On Mon, Jun 2, 2014 at 11:24 AM, <salt...@gmail.com> wrote:

Hi Doug,

I placed some logging in my server to get the timings, then converted the result to a spreadsheet (CSV) that I’ve attached for you. I don’t see any pattern with respect to the URL being requested or the Meetup server being used. The timings seem to be either very short (a few seconds) or very long (just over 30 seconds). I think it’s strange that there aren’t any timings in between these two (i.e. 10 seconds).

This is great! Thanks Dominique. I'll open a ticket to investigate the issue.

 

Dominique

[salt...@gmail.com]

Hi,

FYI: I checked my server log this morning and this problem is still occurring. It occurs throughout the day (i.e. it doesn’t seem to be happening more often at peak times).

Dominique

From: salt...@gmail.com
Sent: ‎Monday‎, ‎2‎ ‎June‎, ‎2014 ‎8‎:‎24‎ ‎AM
To: meetu...@googlegroups.com

Hi Doug,

I placed some logging in my server to get the timings, then converted the result to a spreadsheet (CSV) that I’ve attached for you. I don’t see any pattern with respect to the URL being requested or the Meetup server being used. The timings seem to be either very short (a few seconds) or very long (just over 30 seconds). I think it’s strange that there aren’t any timings in between these two (i.e. 10 seconds).

Dominique

From: Doug Tangren
Sent: ‎Sunday‎, ‎1‎ ‎June‎, ‎2014 ‎9‎:‎30‎ ‎AM
To: meetup-api

[salt...@gmail.com]

Hi,

It’s been about a week now that my site has been unusable due to these delays so I have some angry customers and losing some, I suspect. Can I get an update as to this issue? Have you identified whether this problem affects other API users? Do you have an idea of the cause? Do you have an idea when this will be fixed? Any details you could provide that I can pass on to my customers would be somewhat helpful.

Dominique

[Doug Tangren]

On Jun 7, 2014 1:07 PM, <salt...@gmail.com> wrote:
>
> Hi,
>
> It’s been about a week now that my site has been unusable due to these delays so I have some angry customers and losing some, I suspect. Can I get an update as to this issue? Have you identified whether this problem affects other API users? Do you have an idea of the cause? Do you have an idea when this will be fixed? Any details you could provide that I can pass on to my customers would be somewhat helpful.
>
> Dominique

We are still investigating the issue. We haven't seen any widespread or overall increases in response latencies so the issue my be limited which makes it more difficult to resolve. We we continue looking at this next week.

[Vijay Sharma]

Hi Doug,

Happy to share, just had a lot of work to do the last couple of weeks... We're in the AppStore now, hopefully you'll like how prominent Meetup is in the app, you even have your own pin! :)

https://itunes.apple.com/gb/app/timeplace-browse-real-world./id878263149?mt=8

Let me know what you think, would be happy to discuss improvements to the Meetup side of things with you if you want to email me... :)

Thanks

Vijay

[Doug Tangren]

On Fri, Jun 13, 2014 at 3:09 PM, Vijay Sharma <wij...@gmail.com> wrote:

Hi Doug,

Happy to share, just had a lot of work to do the last couple of weeks... We're in the AppStore now, hopefully you'll like how prominent Meetup is in the app, you even have your own pin! :)

https://itunes.apple.com/gb/app/timeplace-browse-real-world./id878263149?mt=8

Let me know what you think, would be happy to discuss improvements to the Meetup side of things with you if you want to email me... :)

Very nice!

[salt...@gmail.com]

Hi,

This problem seems to have improved for a while starting sometime on the 20th, with connect times down to 5-10 seconds, but then at 2014-06-24 20:22:15 we’re back to getting 30 second connect times fairly consistently. ☹ I hope this issue has a high priority!

Dominique

[Doug Tangren]

On Thu, Jun 26, 2014 at 3:15 AM, <salt...@gmail.com> wrote:

Hi,

This problem seems to have improved for a while starting sometime on the 20th, with connect times down to 5-10 seconds, but then at 2014-06-24 20:22:15 we’re back to getting 30 second connect times fairly consistently. ☹ I hope this issue has a high priority!

Hi Dominique, 

It's definitely one of our top priorities. We're recently launched performance fixes that should have a nice effect on group and event based API endpoints. We should have one out for profiles endpoints soon. Are there are API endpoints that seem particularly slow for you? We are also investigating temporary hikes in response times during our release schedules ( we launch a new version of the site multiple times a day ). I am looking into ways to reduce the impact that has on API response times. Are stats are showing that timings like the ones you are reporting are pretty rare. Most requests are responded to within around 200-300ms. This will continue to be my focus until the issue is fully resolved.

[mike castleman]

hi Dominique,

Are you also able to investigate to be sure it's not something on your
end? We're not seeing especially elevated response times on the Meetup
mobile apps, which also use the public API.

cheers,
mlc

On 06/26/2014 03:15 AM, salt...@gmail.com wrote:
> Hi,
>

> This problem seems to have improved for a while starting sometime on the
> 20th, with connect times down to 5-10 seconds, but then at 2014-06-24
> 20:22:15 we’re back to getting 30 second connect times fairly
> consistently. ☹ I hope this issue has a high priority!
>
> Dominique
>

> *From:* salt...@gmail.com <mailto:salt...@gmail.com>
> *Sent:* ‎Saturday‎, ‎7‎ ‎June‎, ‎2014 ‎10‎:‎05‎ ‎AM
> *To:* meetu...@googlegroups.com <mailto:meetu...@googlegroups.com>

>
> Hi,
>
> It’s been about a week now that my site has been unusable due to these
> delays so I have some angry customers and losing some, I suspect. Can I
> get an update as to this issue? Have you identified whether this problem
> affects other API users? Do you have an idea of the cause? Do you have
> an idea when this will be fixed? Any details you could provide that I
> can pass on to my customers would be somewhat helpful.
>
> Dominique
>

> *From:* salt...@gmail.com <mailto:salt...@gmail.com>
> *Sent:* ‎Thursday‎, ‎5‎ ‎June‎, ‎2014 ‎7‎:‎35‎ ‎AM
> *To:* meetu...@googlegroups.com <mailto:meetu...@googlegroups.com>

>
> Hi,
>
> FYI: I checked my server log this morning and this problem is still
> occurring. It occurs throughout the day (i.e. it doesn’t seem to be
> happening more often at peak times).
>
> Dominique
>

> *From:* salt...@gmail.com <mailto:salt...@gmail.com>
> *Sent:* ‎Monday‎, ‎2‎ ‎June‎, ‎2014 ‎8‎:‎24‎ ‎AM
> *To:* meetu...@googlegroups.com <mailto:meetu...@googlegroups.com>

>
> Hi Doug,
>
> I placed some logging in my server to get the timings, then converted
> the result to a spreadsheet (CSV) that I’ve attached for you. I don’t
> see any pattern with respect to the URL being requested or the Meetup
> server being used. The timings seem to be either very short (a few
> seconds) or very long (just over 30 seconds). I think it’s strange that
> there aren’t any timings in between these two (i.e. 10 seconds).
>
> Dominique
>

> *From:* Doug Tangren <mailto:do...@meetup.com>
> *Sent:* ‎Sunday‎, ‎1‎ ‎June‎, ‎2014 ‎9‎:‎30‎ ‎AM
> *To:* meetup-api <mailto:meetu...@googlegroups.com>

>
>
>
>
> On Sun, Jun 1, 2014 at 5:15 AM, <salt...@gmail.com
> <mailto:salt...@gmail.com>> wrote:
>
> Hi,
>
> My Meetup API script has been running for over a year and I’ve
> noticed recently that it has gotten very slow, so much so that it is
> unusable a majority of the time. I did some investigation and it
> appears that sometimes the requests for data from the Meetup API are
> taking very long, approximately 30 seconds each. Is there some rate
> limiting that was introduced that is causing this? Here is a sample
> of the times for various URLs:
>
> 2014-06-01 02:14:12 ERROR: Duration of
> https://api.meetup.com/2/profile/1993281/8134674?fields=role%2Cstatus&only=role%2Cstatus&access_token=XYZ

> <https://api.meetup.com/2/profile/1993281/8134674?fields=role%2cstatus&only=role%2cstatus&access_token=XYZ>:

> 30.174s
>
>
>
>
> Do these timings directly reflect the time from request to response
> without other factors like retried attempts?
>
> Requests opting for extra fields can result in somewhat slower response
> times due to additional resource usage to fetch the extra data but 30 is
> definitely not an expected latency. Below is an example of the same
> request using a masked, but valid, oauth2 token.
>
> time curl
> "https://api.meetup.com/2/profile/1993281/8134674?fields=role%2Cstatus&only=role%2Cstatus&access_token=..

> <https://api.meetup.com/2/profile/1993281/8134674?fields=role%2cstatus&only=role%2cstatus&access_token=..>."

> {"status":"active","role":"Organizer"}
>
> real0m0.207s
> user0m0.011s
> sys0m0.008s
>
> I will have a closer look into this when I get into the office on Monday
> but in the meantime, can post back with a few things if they are available.
>
> Each response includes a header called "X-Meetup-server". We serve API
> requests from a group of dedicated servers. The X-Meetup-server header
> indicates the name of a specific server within that group.
>
> For instance the following request indicates is was served by the server

> named "api13.int.meetup.com <http://api13.int.meetup.com>".

>
> time curl -i
> "https://api.meetup.com/2/profile/1993281/8134674?fields=role%2Cstatus&only=role%2Cstatus&access_token=..

> <https://api.meetup.com/2/profile/1993281/8134674?fields=role%2cstatus&only=role%2cstatus&access_token=..>."
> 2>/dev/null | grep "X-Meetup-server"
> X-Meetup-server: api13.int.meetup.com <http://api13.int.meetup.com>
>
> real0m0.220s
> user0m0.010s
> sys0m0.008s

>
> If you are able to, for these long response times, can you see if there
> is any consistency in the the X-Meetup-server returned.
>
> I will look into if anything peculiar happened around the time of these
> requests.
>
>
>
> 2014-06-01 02:14:42 ERROR: Duration of
> https://api.meetup.com/2/profile/1993281/8134674?fields=role%2Cstatus&only=role%2Cstatus&access_token=XYZ

> <https://api.meetup.com/2/profile/1993281/8134674?fields=role%2cstatus&only=role%2cstatus&access_token=7c4722b0f7aa45abb347ae4484fecbba>:

> 30.165s
>
> 2014-06-01 02:15:12 ERROR: Duration of
> https://api.meetup.com/2/event/185824662?fields=self&only=group.id%2Cgroup.name%2Cgroup.urlname%2Cid%2Cname%2Cstatus%2Ctime%2Cself.actions%2Cself.rsvp&access_token=XYZ

> <https://api.meetup.com/2/event/185824662?fields=self&only=group.id%2cgroup.name%2cgroup.urlname%2cid%2cname%2cstatus%2ctime%2cself.actions%2cself.rsvp&access_token=7c4722b0f7aa45abb347ae4484fecbba>:

> 30.182s
>
> 2014-06-01 02:15:42 ERROR: Duration of
> https://api.meetup.com/2/events?member_id=self&status=upcoming&time=1402102800000%2C1402117200000&fields=rsvp_rules%2Cself&only=group.id%2Cgroup.name%2Cgroup.urlname%2Cid%2Cname%2Crsvp_rules.guest_limit%2Cstatus%2Ctime%2Cself.actions%2Cself.rsvp&page=300&offset=0&access_token=XYZ

> <https://api.meetup.com/2/events?member_id=self&status=upcoming&time=1402102800000%2c1402117200000&fields=rsvp_rules%2cself&only=group.id%2cgroup.name%2cgroup.urlname%2cid%2cname%2crsvp_rules.guest_limit%2cstatus%2ctime%2cself.actions%2cself.rsvp&page=300&offset=0&access_token=7c4722b0f7aa45abb347ae4484fecbba>:

> 30.203s
>
> 2014-06-01 02:16:13 ERROR: Duration of
> https://api.meetup.com/2/profiles?group_id=1993281&only=member_id%2Cname%2Crole&status=active&member_id=8134674&page=300&offset=0&access_token=XYZ

> <https://api.meetup.com/2/profiles?group_id=1993281&only=member_id%2cname%2crole&status=active&member_id=8134674&page=300&offset=0&access_token=7c4722b0f7aa45abb347ae4484fecbba>:

> 30.192s
>
> 2014-06-01 02:16:43 ERROR: Duration of
> https://api.meetup.com/2/profiles?group_id=3707622&only=member_id%2Cname%2Crole&status=active&member_id=8134674&page=300&offset=0&access_token=XYZ

> <https://api.meetup.com/2/profiles?group_id=3707622&only=member_id%2cname%2crole&status=active&member_id=8134674&page=300&offset=0&access_token=7c4722b0f7aa45abb347ae4484fecbba>:

> 30.296s
>
> 2014-06-01 02:17:13 ERROR: Duration of
> https://api.meetup.com/2/profiles?group_id=3743392&only=member_id%2Cname%2Crole&status=active&member_id=8134674&page=300&offset=0&access_token=XYZ

> <https://api.meetup.com/2/profiles?group_id=3743392&only=member_id%2cname%2crole&status=active&member_id=8134674&page=300&offset=0&access_token=7c4722b0f7aa45abb347ae4484fecbba>:
> 30.173s
>
> Dominique
>


--
mike castleman
android developer, meetup
mailto:m...@meetup.com

[salt...@gmail.com]

Hi Doug,

We are still experiencing the 30 second response times throughout each day. I have performed some other tests around this and it appears that there are times when the connection can take over a minute. I currently have the attached script running on a 5 minute timer on my server and more than half the time the script times out (one minute) while trying to connect. Is it possible that you have some throttling mechanism in place that would result in this type of behavior?

[salt...@gmail.com]

oops, here is the script.

[Doug Tangren]

Hi Dominique,

Sorry to hear about your troubles. We've recently launched some performance patches for 2/events, 2/concierge, 2/profiles, and 2/groups. Is there a particular method that's causing trouble for you? 

Doug Tangren
Meetup Platform Engineer

[salt...@gmail.com]

Hi Doug,

It seems to me there may be two problems here. The original problem I reported was that requests for data from the API were sometimes taking about 30 seconds. The second problem is the inability to connect to the API sometimes. This latter problem I only discovered through testing today and I don’t know how long it has been occurring or whether it is linked to the original problem.

With the original problem the delays are occurring regardless of the method or Meetup server that is being accessed. With the latter problem we are merely trying to make a socket connection so there is no method involved.

[Doug Tangren]

On Mon, Jul 14, 2014 at 7:02 PM, <salt...@gmail.com> wrote:

Hi Doug,

It seems to me there may be two problems here. The original problem I reported was that requests for data from the API were sometimes taking about 30 seconds. The second problem is the inability to connect to the API sometimes. This latter problem I only discovered through testing today and I don’t know how long it has been occurring or whether it is linked to the original problem.

With the original problem the delays are occurring regardless of the method or Meetup server that is being accessed. With the latter problem we are merely trying to make a socket connection so there is no method involved.

Can you send me the IP address of the server you typically issue requests from to do...@meetup.com. This may be an issue with our service proxy provider. If you can forward that along to me. I can have our systems team put you on a whitelist to help make sure that's not the type of issue you are experiencing.

[salt...@gmail.com]

I added the following to my script:

gethostbyname(trim(`hostname`))

and it returned:

192.81.170.12

though I’m not sure this is the IP address you would see on your end.

[Chris Lewis]

Hi Dominique,

Yeah that address won't help much. If you have shell access to the server just ssh to it and run:

curl http://curlmyip.com/

If you don't but your php installation has curl extensions installed (generally the case), run this script on the server:

<?php
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, "http://curlmyip.com/");
curl_setopt($ch, CURLOPT_HEADER, 0);
curl_exec($ch);
curl_close($ch);
?>

Either of these will give us the 3rd party view of your address.

meetup-api+unsubscribe@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/meetup-api?hl=en?hl=en

---
You received this message because you are subscribed to the Google Groups "Meetup API" group.

To unsubscribe from this group and stop receiving emails from it, send an email to meetup-api+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
--
You received this message because you are subscribed to the Google
Groups "Meetup API" group.
To unsubscribe from this group, send email to

meetup-api+unsubscribe@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/meetup-api?hl=en?hl=en

---
You received this message because you are subscribed to the Google Groups "Meetup API" group.

To unsubscribe from this group and stop receiving emails from it, send an email to meetup-api+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
--
You received this message because you are subscribed to the Google
Groups "Meetup API" group.
To unsubscribe from this group, send email to

meetup-api+unsubscribe@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/meetup-api?hl=en?hl=en

---
You received this message because you are subscribed to the Google Groups "Meetup API" group.

To unsubscribe from this group and stop receiving emails from it, send an email to meetup-api+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
--
You received this message because you are subscribed to the Google
Groups "Meetup API" group.
To unsubscribe from this group, send email to

meetup-api+unsubscribe@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/meetup-api?hl=en?hl=en

---
You received this message because you are subscribed to the Google Groups "Meetup API" group.

To unsubscribe from this group and stop receiving emails from it, send an email to meetup-api+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
--
You received this message because you are subscribed to the Google
Groups "Meetup API" group.
To unsubscribe from this group, send email to

meetup-api+unsubscribe@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/meetup-api?hl=en?hl=en

---
You received this message because you are subscribed to the Google Groups "Meetup API" group.

To unsubscribe from this group and stop receiving emails from it, send an email to meetup-api+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
--
You received this message because you are subscribed to the Google
Groups "Meetup API" group.
To unsubscribe from this group, send email to

meetup-api+unsubscribe@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/meetup-api?hl=en?hl=en

---
You received this message because you are subscribed to the Google Groups "Meetup API" group.

To unsubscribe from this group and stop receiving emails from it, send an email to meetup-api+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
--
You received this message because you are subscribed to the Google
Groups "Meetup API" group.
To unsubscribe from this group, send email to

meetup-api+unsubscribe@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/meetup-api?hl=en?hl=en

---
You received this message because you are subscribed to the Google Groups "Meetup API" group.

To unsubscribe from this group and stop receiving emails from it, send an email to meetup-api+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
--
You received this message because you are subscribed to the Google
Groups "Meetup API" group.
To unsubscribe from this group, send email to

meetup-api+unsubscribe@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/meetup-api?hl=en?hl=en

---
You received this message because you are subscribed to the Google Groups "Meetup API" group.

To unsubscribe from this group and stop receiving emails from it, send an email to meetup-api+unsubscribe@googlegroups.com.

[salt...@gmail.com]

Hi Chris,

With your PHP script I get back “192.81.170.12“ which is the same as what I got back using gethostbyname(trim(`hostname`)). I guess this is correct then?

Dominique

meetup-api+...@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/meetup-api?hl=en?hl=en

---
You received this message because you are subscribed to the Google Groups "Meetup API" group.

To unsubscribe from this group and stop receiving emails from it, send an email to meetup-api+...@googlegroups.com.

[Chris Lewis]

Sorry I sped read. 192.168.0.0 is the start of a private range, but yours is not in that range. I'll pass that along and we'll see if that helps.