In reply to a post by seb:

Anyone have any outstanding bugs/issues?

Couple of points, not really bugs:

1) The "Share" button only gives a link to the Live graph, the option for a 24-hour "snapshot" seems to have gone (unless I'm missing something). Will it be coming back? (Please )

2) The arrow to go straight from one BQM to the next disappears after you've done a lap... and there's no back arrow. Fixable? (Please )

Correct. Although I don't have the hourly spikes.

At a guess, a switch/node/route was taken out causing the blip.

In reply to a post by billford:

1) The "Share" button only gives a link to the Live graph, the option for a 24-hour "snapshot" seems to have gone (unless I'm missing something). Will it be coming back? (Please )

Click "Detail & History" then "Share this Day"

In reply to a post by billford:

2) The arrow to go straight from one BQM to the next disappears after you've done a lap... and there's no back arrow. Fixable? (Please )

I don't think I remember that. If you press left/right on keyboard it goes between the different graphs on the same monitor (i.e. LON1 or the original source and EDI1)

That all works, so it was me missing something after all, thanks 👍

I hadn't thought of using the keyboard arrows; I was thinking of the right-pointing arrow on a BQM when you click it to get the enlarged version. Nor had I thought of looking at the history to share a specific day's results, but it does make more sense

In reply to a post by billford:

That all works, so it was me missing something after all, thanks 👍

I hadn't thought of using the keyboard arrows; I was thinking of the right-pointing arrow on a BQM when you click it to get the enlarged version. Nor had I thought of looking at the history to share a specific day's results, but it does make more sense

The arrows are there but faint .. but it still goes between the same monitor not different BQMs

In reply to a post by billford:

That all works, so it was me missing something after all, thanks 👍

I hadn't thought of using the keyboard arrows; I was thinking of the right-pointing arrow on a BQM when you click it to get the enlarged version. Nor had I thought of looking at the history to share a specific day's results, but it does make more sense

btw you should add the EDI1 pings to the monitor not create new monitors.. then it's visible on one URL

seb

In reply to a post by seb:

The arrows are there but faint .. but it still goes between the same monitor not different BQMs

My first thought when I read that was Hmmm..., but it turns out that on my setup they're not faint, they're invisible. Until I move the mouse to roughly the right place, then they show up. Hence why I missed them

In reply to a post by seb:

btw you should add the EDI1 pings to the monitor not create new monitors.. then it's visible on one URL

Yeah, I saw your earlier remark about that, but I'd already set mine up by then. I'll tidy it up shortly.

This is quite interesting. When you say Zen backhaul, what exactly do you mean.

I really want to add automatic tracing for the path from the ping node to the user into this system.

In reply to a post by seb:

When you say Zen backhaul, what exactly do you mean.

Bear in mind that I'm no expert, but as I understood things at the time: when I was on FTTC, Zen were leasing some of BT's (OR's?) fibre bandwidth from the cabinet back to their own network for their own customers; the cabinet was highly populated and congestion (using BT/OR) was fairly frequent so IDNet "sub-leased" some bandwidth from Zen to get my data back to their network, avoiding BT almost entirely... whatever, it worked- the congestion vanished!

I just assumed that something similar would apply with FTTP, but I've no real evidence and never bothered to ask... maybe I should have done, I have a feeling I'm showing my ignorance^* .

I really want to add automatic tracing for the path from the ping node to the user into this system.

Would this be just for your own internal stats or visible to the user? It would be interesting to see what sort of journey my packets go on, and potentially very useful at times



^* Not that I'm too bothered about that, I'm well aware of some huge, sparsely populated areas in my knowledge!

In reply to a post by billford:

In reply to a post by seb:

When you say Zen backhaul, what exactly do you mean.

Bear in mind that I'm no expert, but as I understood things at the time: when I was on FTTC, Zen were leasing some of BT's (OR's?) fibre bandwidth from the cabinet back to their own network for their own customers; the cabinet was highly populated and congestion (using BT/OR) was fairly frequent so IDNet "sub-leased" some bandwidth from Zen to get my data back to their network, avoiding BT almost entirely... whatever, it worked- the congestion vanished!

I just assumed that something similar would apply with FTTP, but I've no real evidence and never bothered to ask... maybe I should have done, I have a feeling I'm showing my ignorance^* .

I'm not exactly sure what IDNet took and where, but I suspect they took a handoff at the telephone exchange or in the region, rather than using BT Wholesale to link back from there to their LNS in a datacentre. This wouldn't cover congestion at the cabinet, but on the backhaul from the telephone exchange. Same would apply to FTTP potentially. It's not really any different to Internet routing except you may not see as much on traces.

In reply to a post by billford:

Would this be just for your own internal stats or visible to the user? It would be interesting to see what sort of journey my packets go on, and potentially very useful at times

There's no reason we wouldn't expose the return traceroute to users if we have it. We can obviously do a trace route on our tools page at any time, anyway if you want it. This would just the benefit of doing it automatically when there's an event or regularly. We have tens of thousands of BQMs, so it's not something that we can do every minute for every BQM, though. We need to think about how they would work.

We have a great internal tool that I've spent some time developing which isn't really in production yet, but I'd like to get a public version of that at some point as well, as it highlights very clearly when there are issues on networks. We're certainly going down the road of analysis more now. I want to get another ping box up quite soon (already agreed with the network hosting it). I'm also trying to get one into Amsterdam but need to find a network (not just one that links it back to LINX).

Once that's done we have another project which is quite exciting

seb