bgpreport

Network · data from 2026-11-12

AS202895 TFnet

Registry name: TFnet TFnet s.r.o., CZ · PeeringDB

10IPv4 routes 0.0% RPKI valid · 90.0% with a route object
1IPv6 routes 0.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
11No 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 AS202895, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS202895, 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.
178.21.187.0/24 No ROA Nonecovered by 178.21.184.0/21 669 99% 67
94.127.128.0/21 No ROA RIR databaseRIPE 672 100% 67
178.21.184.0/21 No ROA RIR databaseRIPE 672 100% 67
178.21.189.0/24 No ROA RIR databaseRIPE 672 100% 67
185.135.4.0/22 No ROA RIR databaseRIPE 672 100% 67
94.127.129.0/24 No ROA RIR databaseRIPE 669 99% 67
94.127.130.0/24 No ROA RIR databaseRIPE 669 99% 67
94.127.133.0/24 No ROA RIR databaseRIPE 669 99% 67
178.21.185.0/24 No ROA RIR databaseRIPE 669 99% 67
178.21.186.0/24 No ROA RIR databaseRIPE 669 99% 67
2a0b:7340::/29 No ROA RIR databaseRIPE 634 100% 67

AS-SET

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

  • ROA: none11
  • Route object: none1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none178.21.187.0/24No ROA covers it. Add a ROA for AS202895, maxLength 24.669 of 673
Route object: none178.21.187.0/24No route object for it. A route object for 178.21.184.0/21 with origin AS202895 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202895 in the RIR database for the space.669 of 673
ROA: none94.127.128.0/21No ROA covers it. Add a ROA for AS202895, maxLength 21.672 of 673
ROA: none178.21.184.0/21No ROA covers it. Add a ROA for AS202895, maxLength 21.672 of 673
ROA: none178.21.189.0/24No ROA covers it. Add a ROA for AS202895, maxLength 24.672 of 673
ROA: none185.135.4.0/22No ROA covers it. Add a ROA for AS202895, maxLength 22.672 of 673
ROA: none94.127.129.0/24No ROA covers it. Add a ROA for AS202895, maxLength 24.669 of 673
ROA: none94.127.130.0/24No ROA covers it. Add a ROA for AS202895, maxLength 24.669 of 673
ROA: none94.127.133.0/24No ROA covers it. Add a ROA for AS202895, maxLength 24.669 of 673
ROA: none178.21.185.0/24No ROA covers it. Add a ROA for AS202895, maxLength 24.669 of 673
ROA: none178.21.186.0/24No ROA covers it. Add a ROA for AS202895, maxLength 24.669 of 673
ROA: none2a0b:7340::/29No ROA covers it. Add a ROA for AS202895, maxLength 29.634 of 636

Route objects not announced

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

94.127.134.0/24RIPENo 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.