[VoiceOps] VoIP Innovations reliability

Sun Mar 20 22:33:22 EDT 2016

You're right. Was this mentioned anywhere other than buried in that
maintenance notification?

On Thu, Mar 17, 2016 at 6:45 PM, Nathan Anderson <nathana at fsr.com> wrote:

> Not true re: DR IP.  Details about it are not being broadcast publicly,
> though, to prevent the attackers from getting their hands on it.  You are
> probably thinking of their primary and secondary SBCs within the main data
> center.  For details about the DR SBC you need to contact VI (or read your
> e-mails).
>
>
>
> -- Nathan
>
>
>
> *From:* VoiceOps [mailto:voiceops-bounces at voiceops.org] *On Behalf Of *Robert
> Johnson
> *Sent:* Thursday, March 17, 2016 3:43 PM
>
> *To:* voiceops at voiceops.org
> *Subject:* Re: [VoiceOps] VoIP Innovations reliability
>
>
>
> Their primary SBC and DR IP are both in the same IP netblock, so whenever
> the DDOS hits, both IPs are affected. The past few outages have involved
> 80% packet loss or so to both hosts, so some calls do make their way
> through, and plenty of wierdness ensues when an INVITE makes its way
> through but not the OK on the way back.
>
>
>
> Can't wait to get our numbers ported out.
>
>
>
> On Thu, Mar 17, 2016 at 6:27 PM, Nate Burke <nate at blastcomm.com> wrote:
>
> Annnd they're down again.
>
>
>
> On 3/17/2016 5:14 PM, Nate Burke wrote:
>
> 6 calls from 4 different CID numbers.  All within 3 minutes.
>
> On 3/17/2016 4:58 PM, Nathan Anderson wrote:
>
> Yesterday I definitely saw calls coming from the DR IP in my logs, but I
> had not yet added that IP as a peerin our SBC.  I'll have to comb through
> logs today to see if we got any.
>
>
>
> Are you saying that the multiple calls you saw coming to your desk were
> all from the same number?  If I had to guess, their side probably sent
> continuous INVITEs to you when it failed to get back an OK for any of them
> (not that you weren't sending back OK, but that their either didn't reach
> their SBC or did not reach it in a timely manner).
>
>
>
> -- Nathan
>
>
>
> *From:* VoiceOps [mailto:voiceops-bounces at voiceops.org
> <voiceops-bounces at voiceops.org>] *On Behalf Of *Jeff Waddell
> *Sent:* Thursday, March 17, 2016 2:53 PM
> *To:* Nate Burke
> *Cc:* voiceops at voiceops.org
> *Subject:* Re: [VoiceOps] VoIP Innovations reliability
>
>
>
> That is the issue a lot of our customers are reporting - where multiple
> calls are sent....
>
>
>
> On Thu, Mar 17, 2016 at 5:49 PM, Nate Burke <nate at blastcomm.com> wrote:
>
> I didn't see any traffic increment on the DR IP Address in my firewall
> rules, but this was odd.  During the 15 minute period, I had probably 5 or
> 6 simultaneous calls ring into my desk.  I normally only take a handfull of
> calls a day.
>
>
>
> On 3/17/2016 4:39 PM, Jeff Waddell wrote:
>
> We implemented it too - I haven't checked to see if any traffic was sent
> across it
>
>
>
>
>
>
>
> On Thu, Mar 17, 2016 at 5:20 PM, Nate Burke <nate at blastcomm.com> wrote:
>
> Only 15 Minutes this time though.  I had implemented the Disaster Recover
> Trunk as mentioned previously, but I didn't seem to be getting any calls
> completed through it.
>
>
>
> On 3/17/2016 4:16 PM, Shripal Daphtary wrote:
>
> Down again!
>
> Thanks,
>
>
>
> Shripal
>
>
> On Mar 16, 2016, at 9:50 AM, Nate Burke <nate at blastcomm.com> wrote:
>
> Looks like it just came back up for me.  Just over 30 min.
>
> Nate
>
> On 3/16/2016 8:45 AM, Shripal Daphtary wrote:
>
> We are experiencing an outage as well.
>
> Thanks,
>
>
>
> Shripal
>
>
> On Mar 16, 2016, at 9:36 AM, Nate Burke <nate at blastcomm.com> wrote:
>
> Problems again this morning?  Looks to be acting the same as it has been.
>
> On 3/11/2016 6:00 PM, Alexander Lopez wrote:
>
> I added them to our monitoring platform, stated getting alarms this past
> hour or so.
>
> Up and down.
>
>
>
> -------- Original message --------
> From: Nathan Anderson <nathana at fsr.com> <nathana at fsr.com>
> Date: 3/11/2016 6:31 PM (GMT-05:00)
> To: 'Nate Burke' <nate at blastcomm.com> <nate at blastcomm.com>,
> voiceops at voiceops.org
> Subject: Re: [VoiceOps] VoIP Innovations reliability
>
> ...aaaaaand we're back.
>
> -- Nathan
>
> -----Original Message-----
> From: VoiceOps [mailto:voiceops-bounces at voiceops.org
> <voiceops-bounces at voiceops.org>] On Behalf Of Nathan Anderson
> Sent: Friday, March 11, 2016 3:30 PM
> To: 'Nate Burke'; voiceops at voiceops.org
> Subject: Re: [VoiceOps] VoIP Innovations reliability
>
> It *feels* like they are under attack again, since I get a response to a
> ping once every 20 or so.
>
> -- Nathan
>
> -----Original Message-----
> From: VoiceOps [mailto:voiceops-bounces at voiceops.org
> <voiceops-bounces at voiceops.org>] On Behalf Of Nathan Anderson
> Sent: Friday, March 11, 2016 3:28 PM
> To: 'Nate Burke'; voiceops at voiceops.org
> Subject: Re: [VoiceOps] VoIP Innovations reliability
>
> Confirmed.
>
> -- Nathan
>
> -----Original Message-----
> From: VoiceOps [mailto:voiceops-bounces at voiceops.org
> <voiceops-bounces at voiceops.org>] On Behalf Of Nate Burke
> Sent: Friday, March 11, 2016 3:26 PM
> To: voiceops at voiceops.org
> Subject: Re: [VoiceOps] VoIP Innovations reliability
>
> Anyone else show them down again right now?  My traceroutes aren't even
> leaving Chicago.  Dying at a Chicago hop on Level3.
>
> Nate
>
> On 3/6/2016 6:50 PM, Nathan Anderson wrote:
> > Did anybody else just suffer another 45-minute-ish long outage from
> about 4:00p PST to 4:45p PST (ending about 5 minutes ago)?
> >
> > -- Nathan
> >
> > -----Original Message-----
> > From: frnkblk at iname.com [mailto:frnkblk at iname.com <frnkblk at iname.com>]
> > Sent: Sunday, March 06, 2016 4:43 PM
> > To: Nathan Anderson; voiceops at voiceops.org
> > Subject: RE: VoIP Innovations reliability
> >
> > More here: http://blog.voipinnovations.com/blog
> >
> > Frank
> >
> > -----Original Message-----
> > From: VoiceOps [mailto:voiceops-bounces at voiceops.org
> <voiceops-bounces at voiceops.org>] On Behalf Of Nathan
> > Anderson
> > Sent: Tuesday, March 01, 2016 8:27 PM
> > To: voiceops at voiceops.org
> > Subject: [VoiceOps] VoIP Innovations reliability
> >
> > Holy schlamoly.  Anybody else use them here and being handed outage after
> > outage over the last 2 days?  Seriously thinking at this point about
> doing
> > something else.  This is ridiculous.
> >
> > I desperately need sleep and if my cell goes off one more time...
> >
> > -- Nathan
> > _______________________________________________
> > VoiceOps mailing list
> > VoiceOps at voiceops.org
> > https://puck.nether.net/mailman/listinfo/voiceops
> >
> >
> >
> > _______________________________________________
> > VoiceOps mailing list
> > VoiceOps at voiceops.org
> > https://puck.nether.net/mailman/listinfo/voiceops
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
>
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
>
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
>
>
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
>
>
>
>
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
>
>
>
>
> _______________________________________________
>
> VoiceOps mailing list
>
> VoiceOps at voiceops.org
>
> https://puck.nether.net/mailman/listinfo/voiceops
>
>
>
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20160320/95973a40/attachment-0001.html>