Skip to content

The peering request that got me a job interview

Networking by HeadRich 6 replies 587 views
#1

But how much RAM was the garage box
Humblebrag: my home lab has 256GB for "BGP simulations"
Seriously though nice pivot
Budget was clearly tight and you still bothered with peering
Respect

#2

The lesson (if there is one) is that admitting mediocrity openly beats pretending expertise. Semicolons separate the honest from the merely confident. I sent seventeen peering requests in 2019. Got three replies, one of which was a legal threat (long story. Their LOA template was ambiguous). The other became a decade-long transit contract. Quantity has its own quality. Maybe too well understood by sales teams already.

9 #3

Mas tipo ninguém acredita né
Eu mandei 50 requests só 2 respostas

1 #4

1. Validation of approach
A) Sent 12 peering requests in 2024
B) 4 replies, 2 meaningful
C) One became a private VLAN at InterServer

2. Key factors
I. Mentioned specific prefix count and traffic ratio
Ii. Admitted we were small (transparency)
Iii. Offered immediate turnup without paperwork drama

3. Counterexample
A) HostHatch never replied
B) CloudCone sent automated "minimum 10Gbps" rejection
C) Their loss; we grew 400% since

4. Recommendation
I. Email everyone
Ii. Expect 80% silence
Iii. The 20% defines your network

#5

256GB ddr4 or ddr5 though

RAID 1: because paranoia pays
#6

Seventeen requests and one legal threat, really

#7

Quantity has its own quality is true

Post a reply

You need an account to reply. Log in or register to join the conversation.

Post reply Preview Save draft