bgpreport

Network · data from 2026-11-12

AS207994 ServCity

Registry name: Blockchain-Creek Blockchain Creek B.V., BE · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS207994, 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.
146.103.50.142/32 Invalid: maxLength Nonecovered by 146.103.50.0/24 2 0%low visibility 1
91.102.165.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
91.198.123.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
5.253.37.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
178.254.177.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
31.57.34.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
62.72.177.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
82.38.96.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
146.103.50.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
163.5.76.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
37.1.226.0/24 Valid RIR databaseRADB, RIPE 670 100% 67
79.182.10.0/24 Valid RIR databaseRADB, RIPE 668 99% 67
31.56.68.0/24 Valid RIR databaseRADB, RIPE 663 99% 67
91.124.98.0/24 Valid RIR databaseRADB, RIPE 30 4%low visibility 17
2a01:ec41::/40 Valid RIR databaseRIPE 27 4%low visibility 12
2a01:ec41::/48 Valid RIR databaseRIPE 27 4%low visibility 12
2a01:ec41:1::/48 Valid RIR databaseRIPE 27 4%low visibility 12
2a01:ec41:2::/48 Valid RIR databaseRIPE 27 4%low visibility 12

AS-SET

PeeringDB's irr_as_set for AS207994: AS207994:AS-BCC-NET. 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 (AS207994 isn't in the set, or no route object for AS207994 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 objectsAS207994 in itNot covered
AS207994:AS-BCC-NET RIPElists itself further down 70124,421 Yes 1

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

  • ROA: maxLength1
  • Route object: none1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: maxLength146.103.50.142/32ROA 146.103.50.0/24 AS207994 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 146.103.50.142/32.2 of 673
Route object: none146.103.50.142/32No route object for it. A route object for 146.103.50.0/24 with origin AS207994 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS207994 in the RIR database for the space.2 of 673

Route objects not announced

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

2a10:2f01:219::/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.