On 2024-03-07 05:08, Pedro Prado wrote:
* I am biased, I’m from Arista * but having said that have you guys experienced
Arista TAC?
Yes.
As you guys said scale may change things down the road, but at the current
scale it’s still an engineer that answers your call, straight away.
I think
To close the loop on this, Verizon Wireless reported to me that they
fixed the issue (whatever it was).
They further said that 63.56.37.4 was a typo; all IPs should have been
in 63.59.x.x.
I am able to reach the 63.59.0.0/16 IPs in question: 63.59.39.232 &
63.59.67.68.
Justin: Thanks for
I see the route originated by two different ASNs. I agree that when I
use the AS6167 path, it is broken (for the destinations where it is
broken; 63.59.166.100 was working despite using the AS6167 path).
BGP routing table entry for 63.59.0.0/16
Paths: 2 available
6939 701 22394
On 2024-02-09 18:10, Justin Krejci wrote:
For a good long while (months) we have had similar issues with various
Verizon destinations.
Only Verizon *Wireless* destinations, or other Verizon *Business* things?
As of today, I'm told (via an upstream provider) that Verizon Business
says this is
On 2024-02-12 18:12, Job Snijders wrote:
On Mon, Feb 12, 2024 at 05:01:35PM -0600, Richard Laager wrote:
On 2024-02-12 15:18, Job Snijders via NANOG wrote:
On Mon, Feb 12, 2024 at 04:07:52PM -0500, Geoff Huston wrote:
I was making an observation that the presentation material was
referring
On 2024-02-12 15:18, Job Snijders via NANOG wrote:
On Mon, Feb 12, 2024 at 04:07:52PM -0500, Geoff Huston wrote:
I was making an observation that the presentation material was
referring to "RPKI-Invalid" while their implementation was using
"ROA-Invalid" There is a difference between these two
-27).
This breaks email between us and it's been MONTHS of VZW getting nowhere.
Based on some traceroutes (on 2023-11-27 and again just now), the
working ones go through 140.222.234.223 (0.ae10.GW7.CHI13.ALTER.NET)
while the broken ones stop at 140.222.234.221 (0.ae9.GW7.CHI13.ALTER.NET).
--
Rich
Does anyone have a contact at CBS, or know which geolocation service
they use for cbs.com TV streaming? CBS has recently started
mis-geolocating us as being in Canada.
--
Richard
Try this:
http://bgpmon.net/
Richard
.
They clearly don't understand that the SpamHaus PBL (unlike other
SpamHaus lists) is not a list of IPs that have sent spam. I'm looking
for someone with a clue that can help me.
Thanks,
Richard Laager
Wikstrom Telephone Company
P.S. Even ignoring the PBL, this policy of not enrolling IP ranges
On Mon, 2011-12-19 at 20:41 -0800, Michael J Wise wrote:
On Dec 19, 2011, at 6:10 PM, Richard Laager wrote:
I'm trying to sign up for Microsoft's Junk Mail Reporting Program.
Multiple representatives keep sending me more-or-less form responses
saying they can't add my dynamic …
Stop
On Mon, 2011-12-19 at 22:58 -0800, Mike Hale wrote:
rantI'm not sure why it's necessary to have all these individual
feedback loop processes anyway. Why can't everyone just send spam
reports to the Abuse handles on the relevant WHOIS record?/rant
Because that only works for organizations who
On Tue, 2011-12-20 at 12:39 +0530, Suresh Ramasubramanian wrote:
On Tue, Dec 20, 2011 at 12:23 PM, Richard Laager rlaa...@wiktel.com wrote:
rantI'm not sure why it's necessary to have all these individual
feedback loop processes anyway. Why can't everyone just send spam
reports to the Abuse
On Wed, 2010-12-29 at 12:32 -0500, Christopher J. Pilkington wrote:
On Tue, Dec 28, 2010 at 06:39:21PM -0600, Richard Laager wrote:
I'm looking for a DNS contact for medicare.gov (and cms.gov). They are
failing DNSSEC validation.
Seeing it still broken, I contacted someone over at Lockheed
I'm looking for a DNS contact for medicare.gov (and cms.gov). They are
failing DNSSEC validation.
Emails to hostmaster, webmaster, and postmaster bounce, as does
dnsad...@rdcms.eds.com (from their SOA) and dnsad...@eds.com (from
eds.com's WHOIS). WHOIS for .gov is essentially empty.
15 matches
Mail list logo
