bgpreport

Network · data from 2026-11-12

AS48463 TRADITIONGROUP Tradition Financial Services Ltd.

Registry name: TRADITIONGROUP Tradition Financial Services Ltd., GB · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS48463, 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.
94.142.189.0/24 No ROA Other origin onlycovered by 94.142.184.0/21 672 100% 67
162.222.208.0/22 No ROA Other IRR onlyRADB 672 100% 67
94.142.184.0/24 No ROA RIR databaseRADB, RIPE 673 100% 67
94.142.185.0/24 No ROA RIR databaseRIPE 673 100% 67
94.142.188.0/24 No ROA RIR databaseRIPE 673 100% 67
194.36.220.0/24 No ROA RIR databaseRADB, RIPE 673 100% 67
94.142.184.0/23 No ROA RIR databaseRIPE 670 100% 67
94.142.187.0/24 No ROA RIR databaseRIPE 666 99% 67

AS-SET

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

  • ROA: none8
  • Route object: none1
  • Route object: RIR1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none94.142.189.0/24No ROA covers it. Add a ROA for AS48463, maxLength 24.672 of 673
Route object: none94.142.189.0/24Route objects for it name AS26540. A route object for 94.142.184.0/21 with origin AS48463 covers it (filters allowing more-specifics accept it). Add a route object with origin AS48463 in the RIR database for the space.672 of 673
ROA: none162.222.208.0/22No ROA covers it. Add a ROA for AS48463, maxLength 22.672 of 673
Route object: RIR162.222.208.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none94.142.184.0/24No ROA covers it. Add a ROA for AS48463, maxLength 24.673 of 673
ROA: none94.142.185.0/24No ROA covers it. Add a ROA for AS48463, maxLength 24.673 of 673
ROA: none94.142.188.0/24No ROA covers it. Add a ROA for AS48463, maxLength 24.673 of 673
ROA: none194.36.220.0/24No ROA covers it. Add a ROA for AS48463, maxLength 24.673 of 673
ROA: none94.142.184.0/23No ROA covers it. Add a ROA for AS48463, maxLength 23.670 of 673
ROA: none94.142.187.0/24No ROA covers it. Add a ROA for AS48463, maxLength 24.666 of 673

Route objects not announced

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

66.151.194.0/24RADBNo ROA
94.142.184.0/21RADBNo 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.