#routingtables β Public Fediverse posts
Live and recent posts from across the Fediverse tagged #routingtables, aggregated by home.social.
-
Some interesting facts I like to share to give those remotely related to the industry an idea on the scale of the #Internet (from the perspective of a network nerd):
BGP routing table entries examined: 994,587
Number of IPv4 prefixes
- w/ valid ROA: 555,410
- w/o valid ROA: 437,967
- w/ invalid ROA: 1.210
Total ASNs: 77,222
Origin-only ASNs: 66,053
Transit ASNs: 11,169All these insights are announced weekly by #apnic . These, and many more insights are available on [thyme.apnic.net]. In my case, I got those updates from the #AFNOG mailing list. Great community service from everyone!
-
Some interesting facts I like to share to give those remotely related to the industry an idea on the scale of the #Internet (from the perspective of a network nerd):
BGP routing table entries examined: 994,587
Number of IPv4 prefixes
- w/ valid ROA: 555,410
- w/o valid ROA: 437,967
- w/ invalid ROA: 1.210
Total ASNs: 77,222
Origin-only ASNs: 66,053
Transit ASNs: 11,169All these insights are announced weekly by #apnic . These, and many more insights are available on [thyme.apnic.net]. In my case, I got those updates from the #AFNOG mailing list. Great community service from everyone!
-
Some interesting facts I like to share to give those remotely related to the industry an idea on the scale of the #Internet (from the perspective of a network nerd):
BGP routing table entries examined: 994,587
Number of IPv4 prefixes
- w/ valid ROA: 555,410
- w/o valid ROA: 437,967
- w/ invalid ROA: 1.210
Total ASNs: 77,222
Origin-only ASNs: 66,053
Transit ASNs: 11,169All these insights are announced weekly by #apnic . These, and many more insights are available on [thyme.apnic.net]. In my case, I got those updates from the #AFNOG mailing list. Great community service from everyone!
-
Some interesting facts I like to share to give those remotely related to the industry an idea on the scale of the #Internet (from the perspective of a network nerd):
BGP routing table entries examined: 994,587
Number of IPv4 prefixes
- w/ valid ROA: 555,410
- w/o valid ROA: 437,967
- w/ invalid ROA: 1.210
Total ASNs: 77,222
Origin-only ASNs: 66,053
Transit ASNs: 11,169All these insights are announced weekly by #apnic . These, and many more insights are available on [thyme.apnic.net]. In my case, I got those updates from the #AFNOG mailing list. Great community service from everyone!
-
Some interesting facts I like to share to give those remotely related to the industry an idea on the scale of the #Internet (from the perspective of a network nerd):
BGP routing table entries examined: 994,587
Number of IPv4 prefixes
- w/ valid ROA: 555,410
- w/o valid ROA: 437,967
- w/ invalid ROA: 1.210
Total ASNs: 77,222
Origin-only ASNs: 66,053
Transit ASNs: 11,169All these insights are announced weekly by #apnic . These, and many more insights are available on [thyme.apnic.net]. In my case, I got those updates from the #AFNOG mailing list. Great community service from everyone!
-
CW: #SDN #MITM attempt #InfosecExchange #infosec #traceback 1 of 3
@jerry π€ππ€π€π¨
#InfosecExchange #SDNTracebackHost caught trying to manipulate #routingtables to redirect through #AWS for #MITM
/ 1 of 3 hosts caught / #infosec #infosec_jcp #tracebacks
ec2-35-160-233-103.us-west-2.compute.amazonaws.com
-
CW: #SDN #MITM attempt #InfosecExchange #infosec #traceback 1 of 3
@jerry π€ππ€π€π¨
#InfosecExchange #SDNTracebackHost caught trying to manipulate #routingtables to redirect through #AWS for #MITM
/ 1 of 3 hosts caught / #infosec #infosec_jcp #tracebacks
ec2-35-160-233-103.us-west-2.compute.amazonaws.com
-
CW: #SDN #MITM attempt #InfosecExchange #infosec #traceback 1 of 3
@jerry π€ππ€π€π¨
#InfosecExchange #SDNTracebackHost caught trying to manipulate #routingtables to redirect through #AWS for #MITM
/ 1 of 3 hosts caught / #infosec #infosec_jcp #tracebacks
ec2-35-160-233-103.us-west-2.compute.amazonaws.com
-
CW: #SDN #MITM attempt #InfosecExchange #infosec #traceback 1 of 3
@jerry π€ππ€π€π¨
#InfosecExchange #SDNTracebackHost caught trying to manipulate #routingtables to redirect through #AWS for #MITM
/ 1 of 3 hosts caught / #infosec #infosec_jcp #tracebacks
ec2-35-160-233-103.us-west-2.compute.amazonaws.com
-
CW: #SDN #MITM attempt #InfosecExchange #infosec #traceback 1 of 3
@jerry π€ππ€π€π¨
#InfosecExchange #SDNTracebackHost caught trying to manipulate #routingtables to redirect through #AWS for #MITM
/ 1 of 3 hosts caught / #infosec #infosec_jcp #tracebacks
ec2-35-160-233-103.us-west-2.compute.amazonaws.com