bgpreport

Network · data from 2026-11-12

AS57332 TOM NET

Registry name: TOM-NET-AS TOM-NET s.c. Dariusz Koper, Radoslaw Koper, PL · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS57332, 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.
5.206.240.0/20 Valid RIR databaseRIPE 671 100% 68
159.255.176.0/20 Valid RIR databaseRIPE 671 100% 68
45.85.8.0/22 Valid RIR databaseRIPE 668 99% 67
159.255.180.0/23 Valid RIR databaseRIPE 22 3%low visibility 23
159.255.186.0/24 Valid RIR databaseRIPE 22 3%low visibility 23
159.255.187.0/24 Valid RIR databaseRIPE 22 3%low visibility 23

AS-SET

AS57332's PeeringDB record names no AS-SET.

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

  • Route object: not announced15

Route objects not announced

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

5.206.240.0/21RIPEInvalid: maxLength
5.206.248.0/21RIPEInvalid: maxLength
159.255.176.0/21RIPEInvalid: maxLength
159.255.184.0/21RIPEInvalid: maxLength
2001:470:174::/48ARINValid
2001:470:23d::/48ARINValid
2001:470:2a1::/48ARINValid
2001:470:427::/48ARINValid
2001:470:44c::/48ARINValid
2001:470:4bd::/48ARINValid
2001:470:542::/48ARINValid
2001:470:647::/48ARINValid
2a00:5f20::/32RIPENo ROA
2a10:f781:10:243::/64RIPENo ROA
2a10:f781:10:c2aa::/64RIPENo 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.