bgpreport

Network · data from 2026-11-12

AS214497 Whitelabel Solutions, Ltd.

Registry name: WHITELABEL Whitelabel Solutions, Ltd., IL · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS214497, 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.

2a10:ccc7:b110::/44 No ROA None 629 99% 68
2a06:de07:fc00::/44 No ROA RIR databaseRIPE 632 99% 69
2a14:7c0:1740::/48 Valid RIR databaseRIPE 632 99% 69

AS-SET

PeeringDB's irr_as_set for AS214497: AS214497:AS-CUST. 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 (AS214497 isn't in the set, or no route object for AS214497 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 objectsAS214497 in itNot covered
AS214497:AS-CUST RIPElists itself further down4 member sets in no database: AS198351:AS-SECUREWAN, AS199746:AS-NEXTSERV, AS208191:AS-GOHOST, AS213465:AS-RAINBOW 121122,972 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 8 are in fix.csv.

  • ROA: none2
  • Route object: none1
  • AS-SET: missing member4
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none2a10:ccc7:b110::/44No ROA covers it. Add a ROA for AS214497, maxLength 44.629 of 636
Route object: none2a10:ccc7:b110::/44No route object for it. Add a route object with origin AS214497 in the RIR database for the space.629 of 636
ROA: none2a06:de07:fc00::/44No ROA covers it. Add a ROA for AS214497, maxLength 44.632 of 636
AS-SET: missing memberAS214497:AS-CUSTAS214497:AS-CUST (RIPE) lists AS198351:AS-SECUREWAN; no IRR database read has it.
AS-SET: missing memberAS214497:AS-CUSTAS214497:AS-CUST (RIPE) lists AS199746:AS-NEXTSERV; no IRR database read has it.
AS-SET: missing memberAS214497:AS-CUSTAS214497:AS-CUST (RIPE) lists AS208191:AS-GOHOST; no IRR database read has it.
AS-SET: missing memberAS214497:AS-CUSTAS214497:AS-CUST (RIPE) lists AS213465:AS-RAINBOW; no IRR database read has it.

Route objects not announced

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

2a14:c380:c00::/44RIPENo 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.