bgpreport

Network · data from 2026-11-12

AS61337 Single Mode Networks Ltd

Registry name: ECOM-AS Single Mode Networks Ltd, GB · PeeringDB

12IPv4 routes 75.0% RPKI valid · 91.7% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
3No ROA 1 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
6Route objects not announced registered with origin AS61337, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS61337, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
83.150.250.0/23 No ROA Other origin onlycovered by 83.150.248.0/22 671 100% 67
83.150.249.0/24 No ROA RIR databaseRIPE 671 100% 67
193.26.23.0/24 No ROA RIR databaseRIPE 671 100% 67
45.153.132.0/23 Valid RIR databaseRIPE 671 100% 67
85.199.212.0/22 Valid RIR databaseRIPE 671 100% 67
91.230.243.0/24 Valid RIR databaseRIPE 671 100% 67
194.55.0.0/24 Valid RIR databaseRIPE 671 100% 67
194.55.40.0/24 Valid RIR databaseRIPE 671 100% 67
194.55.43.0/24 Valid RIR databaseRIPE 671 100% 67
194.60.198.0/23 Valid RIR databaseRIPE 671 100% 67
195.66.148.0/23 Valid RIR databaseRIPE 671 100% 67
45.153.134.0/24 Valid RIR databaseRIPE 670 100% 67
2001:67c:504::/48 Valid RIR databaseRIPE 636 100% 67

AS-SET

PeeringDB's irr_as_set for AS61337: AS-GXT. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS61337 isn't in the set, or no route object for AS61337 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS61337 in itNot covered
AS-GXT RIPElists itself further down 4114265 Yes 0

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 10 are in fix.csv.

  • ROA: none3
  • Route object: none1
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none83.150.250.0/23No ROA covers it. Add a ROA for AS61337, maxLength 23.671 of 673
Route object: none83.150.250.0/23Route objects for it name AS60255. A route object for 83.150.248.0/22 with origin AS61337 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61337 in the RIR database for the space.671 of 673
ROA: none83.150.249.0/24No ROA covers it. Add a ROA for AS61337, maxLength 24.671 of 673
ROA: none193.26.23.0/24No ROA covers it. Add a ROA for AS61337, maxLength 24.671 of 673

Route objects not announced

Route objects with origin AS61337 whose prefix no peer sees AS61337 announce. Many are kept on purpose (backup routes, space announced only in some places).

44.30.228.0/24RADBNo ROA
44.127.128.0/24RIPE-NONAUTHNo ROA
45.153.132.0/22RIPENo ROA
83.150.248.0/22RIPENo ROA
83.150.248.0/24RIPENo ROA
2001:67c:72c::/48RIPENo ROA

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.