bgpreport

Network · data from 2026-11-12

AS209874 TECHTIDE Tech Tide Portugal Unipessoal LDA

Registry name: TECHTIDE Tech Tide Portugal Unipessoal LDA, PT · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS209874, 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.
2a12:bec4:1660::/48 No ROA None 633 100% 67
2a14:c380:500::/48 Valid None 635 100% 69
5.231.82.0/24 Valid RIR databaseRIPE 673 100% 67
5.231.96.0/24 Valid RIR databaseRIPE 673 100% 67
165.217.161.0/24 Valid RIR databaseRIPE 673 100% 67
165.217.162.0/24 Valid RIR databaseRIPE 673 100% 67
165.217.163.0/24 Valid RIR databaseRIPE 673 100% 67
194.62.122.0/24 Valid RIR databaseRIPE 673 100% 67
5.83.142.0/24 Valid RIR databaseRIPE 672 100% 67
5.83.150.0/24 Valid RIR databaseRIPE 672 100% 67
5.175.174.0/24 Valid RIR databaseRIPE 672 100% 66
5.175.217.0/24 Valid RIR databaseRIPE 672 100% 66
77.90.39.0/24 Valid RIR databaseRIPE 672 100% 67
87.239.129.0/24 Valid RIR databaseRIPE 672 100% 66
89.144.50.0/24 Valid RIR databaseRIPE 672 100% 67
94.103.167.0/24 Valid RIR databaseRIPE 672 100% 66
94.249.150.0/24 Valid RIR databaseRIPE 672 100% 66
94.249.153.0/24 Valid RIR databaseRIPE 672 100% 66
94.249.197.0/24 Valid RIR databaseRIPE 672 100% 66
5.231.25.0/24 Valid RIR databaseRIPE 671 100% 66
2a09:54c3:a000::/40 Valid RIR databaseRIPE 634 100% 69
2a09:54c3:a200::/40 Valid RIR databaseRIPE 634 100% 67
2a12:bec4:1651::/48 Valid RIR databaseRIPE 634 100% 69
2a12:bec4:1652::/48 Valid RIR databaseRIPE 634 100% 69
2a12:bec4:1654::/48 Valid RIR databaseRIPE 634 100% 69
2a12:bec4:1655::/48 Valid RIR databaseRIPE 634 100% 69
2a12:bec4:1656::/48 Valid RIR databaseRIPE 634 100% 69
2a12:bec4:1658::/48 Valid RIR databaseRIPE 634 100% 69
2a12:bec4:1659::/48 Valid RIR databaseRIPE 634 100% 69
2a12:bec4:1520::/48 Valid RIR databaseRIPE 632 99% 67
2a12:bec4:1521::/48 Valid RIR databaseRIPE 632 99% 67
2a12:bec4:1523::/48 Valid RIR databaseRIPE 632 99% 67
2a12:bec4:152d::/48 Valid RIR databaseRIPE 632 99% 67
2a12:bec4:152e::/48 Valid RIR databaseRIPE 632 99% 67
2a12:bec4:152f::/48 Valid RIR databaseRIPE 632 99% 67
2a12:bec4:1653::/48 Valid RIR databaseRIPE 632 99% 67
2a14:7583:8510::/48 Valid RIR databaseRIPE 626 98% 67

AS-SET

AS209874 isn't in PeeringDB, where networks name their 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 6 are in fix.csv.

  • ROA: none1
  • Route object: none2
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none2a12:bec4:1660::/48No ROA covers it. Add a ROA for AS209874, maxLength 48.633 of 636
Route object: none2a12:bec4:1660::/48No route object for it. Add a route object with origin AS209874 in the RIR database for the space.633 of 636
Route object: none2a14:c380:500::/48No route object for it. Add a route object with origin AS209874 in the RIR database for the space.635 of 636

Route objects not announced

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

2a12:bec4:1522::/48RIPEValid
2a12:bec4:1657::/48RADBValid
2a14:7583:8500::/40RIPEInvalid: 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.