bgpreport

Network · data from 2026-11-12

AS35537 xTom Estonia Legacy

Registry name: XTOM-35537 xTom GmbH, DE · PeeringDB

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

Announced routes

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

2a09:7:2004::/48 Valid RIR databaseRADB, RIPE 634 100% 69

AS-SET

PeeringDB's irr_as_set for AS35537: RADB::AS-XTOM. 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 (AS35537 isn't in the set, or no route object for AS35537 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 objectsAS35537 in itNot covered
RADB::AS-XTOM RADB3 member sets in no database: AS-EOIX, AS917:AS-CORE, AS917:AS-CUSTOMERS 1,1592945,706 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 6 are in fix.csv.

  • AS-SET: missing member3
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
AS-SET: missing memberRADB::AS-XTOMAS-XTOM (RADB) lists AS-EOIX; no IRR database read has it.
AS-SET: missing memberRADB::AS-XTOMAS-XTOM (RADB) lists AS917:AS-CORE; no IRR database read has it.
AS-SET: missing memberRADB::AS-XTOMAS-XTOM (RADB) lists AS917:AS-CUSTOMERS; no IRR database read has it.

Route objects not announced

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

45.132.236.0/22RADBNo ROA
2a04:6f01:1::/48RADB, RIPEValid
2a04:6f01:2::/48RIPEInvalid: origin

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.