bgpreport

Network · data from 2026-11-12

AS206885 Tech9 Computer Solutions

Registry name: TECH9COMPUTERS Tech9 Computer Solutions, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS206885, 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.
2a06:e881:1802::/48 No ROA Nonecovered by 2a06:e881:1800::/44 3 0%low visibility 3
2a06:e881:1803::/48 No ROA Nonecovered by 2a06:e881:1800::/44 3 0%low visibility 3
44.124.8.0/24 No ROA Other IRR onlyRADB 672 100% 67
2620:13e:500f::/48 Valid Nonecovered by 2620:13e:5000::/44 3 0%low visibility 3
2001:678:284::/48 Valid RIR databaseRADB, RIPE 633 100% 68

AS-SET

AS206885'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 11 are in fix.csv.

  • ROA: none3
  • Route object: none3
  • Route object: RIR1
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none2a06:e881:1802::/48No ROA covers it. Add a ROA for AS206885, maxLength 48.3 of 636
Route object: none2a06:e881:1802::/48No route object for it. A route object for 2a06:e881:1800::/44 with origin AS206885 covers it (filters allowing more-specifics accept it). Add a route object with origin AS206885 in the RIR database for the space.3 of 636
ROA: none2a06:e881:1803::/48No ROA covers it. Add a ROA for AS206885, maxLength 48.3 of 636
Route object: none2a06:e881:1803::/48No route object for it. A route object for 2a06:e881:1800::/44 with origin AS206885 covers it (filters allowing more-specifics accept it). Add a route object with origin AS206885 in the RIR database for the space.3 of 636
ROA: none44.124.8.0/24No ROA covers it. Add a ROA for AS206885, maxLength 24.672 of 673
Route object: RIR44.124.8.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: none2620:13e:500f::/48No route object for it. A route object for 2620:13e:5000::/44 with origin AS206885 covers it (filters allowing more-specifics accept it). Add a route object with origin AS206885 in the RIR database for the space.3 of 636

Route objects not announced

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

205.207.255.0/24ARINValid
2620:13e:5000::/44ARIN, RADBValid
2a06:8187:fe03::/48RADBNo ROA
2a06:e881:1800::/44RADB, RIPENo 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.