bgpreport

Network · data from 2026-11-12

AS212144 FUTURE-NETWORK-01 trafficforce, UAB

Registry name: FUTURE-NETWORK-01 trafficforce, UAB, LT · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS212144, 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:dc04::/32 Invalid: origin None 2 0%low visibility 2
2a09:dc06::/32 Invalid: origin None 2 0%low visibility 2
2a10:77c0::/29 Invalid: origin None 2 0%low visibility 2
2a12:7700::/29 Valid None 632 99% 68
94.154.118.0/24 Valid RIR databaseRIPE 672 100% 67
2a10:b540::/29 Valid RIR databaseRIPE 633 100% 69

AS-SET

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

  • ROA: origin3
  • Route object: none4
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: origin2a09:dc04::/32ROAs covering it name AS6079, AS397651, not AS212144. If AS212144 should announce it, add a ROA for AS212144.2 of 636
Route object: none2a09:dc04::/32No route object for it. Add a route object with origin AS212144 in the RIR database for the space.2 of 636
ROA: origin2a09:dc06::/32ROAs covering it name AS6079, AS397651, not AS212144. If AS212144 should announce it, add a ROA for AS212144.2 of 636
Route object: none2a09:dc06::/32No route object for it. Add a route object with origin AS212144 in the RIR database for the space.2 of 636
ROA: origin2a10:77c0::/29An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS212144 should announce it, add a ROA for AS212144.2 of 636
Route object: none2a10:77c0::/29No route object for it. Add a route object with origin AS212144 in the RIR database for the space.2 of 636
Route object: none2a12:7700::/29No route object for it. Add a route object with origin AS212144 in the RIR database for the space.632 of 636

Route objects not announced

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

2a12:cac0::/29RADBNo ROA
2a14:c886::/33RIPEValid

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.