et-route-around-damage-baltic-sea-cable-cuts/
.
I hope this audience finds that interesting.
kind regards,
Emile Aben
RIPE NCC
+ no ROA
Kind regards,
Emile Aben
RIPE NCC
Hi NANOG,
in light of a recent discussion on RIS-live, and a question on where
best have RIS peers, this might be of interest to the NANOG crowd:
https://labs.ripe.net/Members/emileaben/how-diverse-is-ris
best regards,
Emile Aben
RIPE NCC
On 17/09/15 15:58, Jared Mauch wrote:
>
>> On Sep 17, 2015, at 9:55 AM, Colin Johnston wrote:
>>
>> anyone tried ripe atlas to see effect :)
I've not looked at RIPE Atlas data, but we do have a near-realtime
monitor on BGP data in RIPEstat, where we map resources to a country:
https://stat.ripe
block is set aside to facilitate IPv6 deployment.
It is subject to a minimum size allocation of /28 and a maximum size
allocation of /24
best regards,
Emile Aben
RIPE NCC
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 31/03/15 19:24, Jared Mauch wrote:
> On Tue, Mar 31, 2015 at 08:19:11PM +0300, Mehmet Akcin wrote:
>> Hello
>>
>> Today March 31 , 2015 GMT +0200 1030am-4pm Turkey has suffered a
>> major power outage impacting nearly 70M people. I am writing a
>
-of-longer-than-24-ipv4-prefixes
Spoiler: the longer-than-/24 prefixes are not very visible/reachable.
Having route-objects improves visibility/reachability, but only a
little bit.
cheers,
Emile Aben
RIPE NCC
-BEGIN PGP SIGNATURE-
Version
bs.ripe.net/Members/emileaben/typhoon-haiyan-what-we-see-in-ripestat-and-ripe-atlas
We will keep an eye out on it.
best regards,
Emile Aben
RIPE NCC
> Satellite: http://www.pagasa.dost.gov.ph/wb/sat_images/satpic.jpg
> http://www.usatoday.com/story/news/world/2013/11/07/philippine
me of a web site, please. it
> will seriously 'inform' some discussion going back and forth on ietf
> lists.
This is now published on RIPE Labs. For the adventurous:
https://labs.ripe.net/Members/emileaben/ripe-atlas-packet-size-matters
regards,
Emile Aben
RIPE NCC
On 26/09/2013 12:23, Emile Aben wrote:
> On 26/09/2013 03:04, Patrick W. Gilmore wrote:
>> It's not a fiber cut. It did come back for a while at least.
>>
>> <https://twitter.com/akamai_soti/status/382872513761398785/photo/1>
>>
>>
> This
sudan-internet-disruptions
near-realtime stats of visibility of Sudanese prefixes and ASNs:
https://stat.ripe.net/SD#tabId=routing
Looks like the number of prefixes went up to about normal again the
last hour or so.
best regards,
Emile Aben
RIPE NCC
s that didn't get any of the 5 pkts that were
sent. Note that there is a large baseline failure rate in IPv6 on RIPE
Atlas probes [1], which would explain the ~10% failure rate for the
smaller packets.
I plan to do more analysis and start writing this up on RIPE Labs over
the next few days.
>From a test last week from all RIPE Atlas probes to a single "known
good" MTU 1500 host I compared probes where I had both a ping test with
ipv4.len 1020 and ipv4.len 1502.
behind NAT probes: 12% 1020 bytes ping worked while 1502 failed
non-NATted probes: 6%""
hth,
Emile Aben
RIPE NCC
On 29/08/2013 04:22, Owen DeLong wrote:
> Has the path MTU been measured for all vantage point pairs?
I didn't, but see
http://www.nlnetlabs.nl/downloads/publications/pmtu-black-holes-msc-thesis.pdf
Fig 23 (page 24) for path MTU data from roughly a year ago (thanks
Benno for posting that link).
On 28/08/2013 08:05, Tore Anderson wrote:
> * Owen DeLong
>
>> On Aug 27, 2013, at 07:33 , valdis.kletni...@vt.edu wrote:
>>
>>> Saku Ytti and Emile Aben have numbers that say otherwise. And there must
>>> be a significantly bigger percentage of failures than
at least 1 reply for the 48 byte ping.
Measurement IDs in RIPE Atlas are 1019675 and 1019676.
Emile Aben
RIPE NCC
analysis at <http://bgpmon.net/blog/?p=540>
We used DNSMON data to analyse this event, and found an earlier leak on
29 and 30 September:
https://labs.ripe.net/Members/emileaben/f-root-route-leak-the-dnsmon-view
best regards,
Emile Aben
RIPE NCC
17 matches
Mail list logo
