bgpreport

Network · data from 2026-11-12

AS207551 speedium

Registry name: as-speedium Wijnand Schouten, NL · PeeringDB

9IPv4 routes 77.8% RPKI valid · 77.8% with a route object
3IPv6 routes 100.0% RPKI valid · 100.0% with a route object
2RPKI invalid 0 origin · 2 maxLength
0No ROA 2 with no route object for this origin
5Low visibility seen by under 10% of full-table peers
3Route objects not announced registered with origin AS207551, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS207551, 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.
117.55.199.29/32 Invalid: maxLength Nonecovered by 117.55.199.0/24 1 0%low visibility 1
117.55.199.204/32 Invalid: maxLength Nonecovered by 117.55.199.0/24 1 0%low visibility 1
194.54.146.0/24 Valid RIR databaseRIPE 314 47% 63
194.164.87.0/24 Valid RIR databaseRIPE 311 46% 63
117.55.199.0/24 Valid RIR databaseRIPE 310 46% 63
89.35.53.0/24 Valid RIR databaseRIPE 307 46% 63
202.181.153.0/24 Valid RIR databaseRIPE 307 46% 63
203.28.15.0/24 Valid RIR databaseRIPE 307 46% 63
212.6.53.0/24 Valid RIR databaseRIPE 307 46% 63
2a10:2080::/48 Valid RIR databaseRIPE 19 3%low visibility 14
2a10:2080:1::/48 Valid RIR databaseRIPE 19 3%low visibility 14
2a10:2080:2::/48 Valid RIR databaseRIPE 19 3%low visibility 14

AS-SET

PeeringDB's irr_as_set for AS207551: RIPE::AS-SPEEDIUM. 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 (AS207551 isn't in the set, or no route object for AS207551 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 objectsAS207551 in itNot covered
RIPE::AS-SPEEDIUM RIPE 1113 Yes 2

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 7 are in fix.csv.

  • ROA: maxLength2
  • Route object: none2
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: maxLength117.55.199.29/32ROA 117.55.199.0/24 AS207551 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 117.55.199.29/32.1 of 673
Route object: none117.55.199.29/32No route object for it. A route object for 117.55.199.0/24 with origin AS207551 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS207551 in the RIR database for the space.1 of 673
ROA: maxLength117.55.199.204/32ROA 117.55.199.0/24 AS207551 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 117.55.199.204/32.1 of 673
Route object: none117.55.199.204/32No route object for it. A route object for 117.55.199.0/24 with origin AS207551 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS207551 in the RIR database for the space.1 of 673

Route objects not announced

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

89.35.53.255/32RIPEInvalid: maxLength
2a10:2080::/29RIPEValid
2a10:2080:3::/64RIPEInvalid: maxLength

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.