Re: Rogers 2022 network outage, Xona Report

Jean-Francois, Comments in line. On Fri, Aug 2, 2024, 22:59 Jean-Francois Mezei wrote: > On 2024-08-02 21:39, Jean-Francois Mezei wrote: > > > Following process, redacted portions of the XONA Partners report have > > been published. > > > > https://crtc.gc.ca/otf/eng/2022/8000/c12-202203868.htm

Re: Rogers 2022 network outage, Xona Report

On 2024-08-02 21:39, Jean-Francois Mezei wrote: > Following process, redacted portions of the XONA Partners report have > been published. > > https://crtc.gc.ca/otf/eng/2022/8000/c12-202203868.htm I have some question on terminology: (pardon my newbieness, just wanting to be pedantic on termino

Rogers 2022 network outage, Xona Report

After a July 2022 outage that caused the whole Rogers network to go down for an extended period (bring down the single homed Interac payment system with it across Canada), political pressure caused CRTC to have a process to look into it. Part of it was the commissioning of a report by experts. Fo

Re: Norms and Standards

> On Aug 3, 2024, at 01:03, Howard, Lee via NANOG wrote: > > If a group of people can pick one topic and start documenting best practices, > we may be able to do something good. I’m not worried about process yet: > content first. There is a long history of the operational community engaging

Re: RIPEstats apparently broken

What would be really convenient was to propagate the internal HTTP error to the external handler. It's returning HTTP 200 with this in the body: "status": "error", "status_code": 500, Returning HTTP 500 would have made my script happier, as it would move ahead without that data. But because it

Re: RIPEstats apparently broken

On Fri, 2 Aug 2024 at 13:49, Rubens Kuhl wrote: > > This is what the example query from > https://stat.ripe.net/docs/02.data-api/announced-prefixes.html is > returning: https://status.ripe.net/ - they know and are working to fix things.

Re: RIPEstats apparently broken

RIPE conveniently has a status page for this exact incident https://status.ripe.net/incidents/8jm3b6j26kcf -- Peter On Fri, Aug 2, 2024 at 4:51 PM Rubens Kuhl wrote: > This is what the example query from > https://stat.ripe.net/docs/02.data-api/announced-prefixes.html is > returning: > > { >

Re: RIPEstats apparently broken

On Fri 2024-08-02 17:48:17-0300 Rubens wrote: > I would assume this was not intentional... are any other users out > there affected by this issue ? I have a custom nagios check, ripestat_monitor_routes.py, that has been returning HTTP Error 500: Internal Server Error for about 8 hours. Regards,

RIPEstats apparently broken

This is what the example query from https://stat.ripe.net/docs/02.data-api/announced-prefixes.html is returning: { "messages": [ [ "error", "There was a problem handling this request. The error has been logged and we will look into the cause as soon as possible. We apologise for

Re: Norms and Standards

If folks think it might be helpful I can get an instance of "allourideas " running. We can deploy one for either (1) gathering ideas on what to work on or (2) aggregating best practices. The apps are helpful in (1) gathering ideas and (2) providi

Re: Wi-Fi Calling in a corporate environment

I've had issues with wifi calling on Palo Alto as well as delayed SMS delivery and receive. I had to allow port 500 and 4500 out to get this working properly. I am planning on trying to implement a whitelist using IPs/domains in the future. --Brendan On Fri, Aug 2, 2024, 12:26 wrote: > Thanks

RE: Wi-Fi Calling in a corporate environment

Thanks all. Oddly enough, it seems that the entire site’s userbase suddenly started working. From what I understand no action was taken to fix anything. So unless a dynamic PaloAlto update broke it and then unbroke it later, I’m not sure what was going on. I’ll debug a bit to know what a wor

Re: Norms and Standards

Hi, I would like to volunteer to help with bullet two: “DDoS mitigation. BCP38, communities for RTBH, packet scrubbing, etc. What can we do collectively?”. -Rich From: NANOG on behalf of Howard, Lee via NANOG Date: Friday, August 2, 2024 at 12:05 PM To: NANOG list Subject: Norms and Standar

Re: Wi-Fi Calling in a corporate environment

My understanding has been that generally, if the cellular network signal was above a certain threshold, phones won't even attempt to use wifi calling. Some carriers used to let you flip a switch to force the phone to prefer wifi over cellular, but some have removed that. ( Verizon for example. ) I

Weekly Global IPv4 Routing Table Report

This is an automated weekly mailing describing the state of the Global IPv4 Routing Table as seen from APNIC's router in Japan. The posting is sent to APOPS, NANOG, AfNOG, SANOG, PacNOG, SAFNOG UKNOF, TZNOG, MENOG, BJNOG, SDNOG, CMNOG, LACNOG and the RIPE Routing WG. Daily listings are sent to bg

Norms and Standards

Last October at NANOG89 in San Diego, John Curran exhorted us to work together to document best practices before governments developed their own. John pointed out that in many industries, technical requirements and standards inform public policy goal

Re: Wi-Fi Calling in a corporate environment

Wi-Fi calling is pretty much an IPsec VPN from the cellular device to the carrier. While I don't have a list of IPs some quick googling did find some form post with domain names and IPs block for some carriers. The main thing is making sure IPsec is not blocked or is otherwise not interfered with

Re: Wi-Fi Calling in a corporate environment

I’ve seen if there’s too much buffering or some sort of other issues it drop out and not work. I’ve actually replaced customer CPE to address this. You want to make sure that you are passing ESP through, and there’s even issues with some of the carriers not liking a phone using wifi calling if

Wi-Fi Calling in a corporate environment

Hey all, Question if anyone knows about cell phone wi-fi calling in US. Googling isn't finding what I'm looking for. We have a corporate site in US where users have BYOD capability, and use their phones with wi-fi calling enabled. Site uses a single NAT address (IPv4) for BYOD

NANOG Announcing 92 Keynotes + More

*Announcing NANOG 92 Keynotes!* *Geoff Huston + Hugh Holbrook To Take the NANOG 92 Stage* *Keynote: Whatever Happened to IPv6? — Geoff Huston - APNIC* We seem to have lost our way - some twenty years ago there was a clear common purpose that we were performing a transition to take the Internet fr

Amazon peering request help

Hi, I’m trying to create a peering request on interconnect.amazon but when I reach “step 3” (contact email) and when I try the “Create” button (last step) I’m getting “Error: Too many requests”. It seems some API behind the peering request form is broken… Anyone listening here can help? Best r