bgpreport

Network · data from 2026-11-12

AS48075 SWIFTASN S.W.I.F.T. SC

Registry name: SWIFTASN S.W.I.F.T. SC, BE · not in PeeringDB

17IPv4 routes 58.8% RPKI valid · 100.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
7No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
20Route objects not announced registered with origin AS48075, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS48075, 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.

149.134.180.0/24 No ROA Other IRR onlyRADB 672 100% 67
149.134.178.0/24 No ROA RIR databaseNTTCOM, RIPE 673 100% 67
149.134.174.0/24 No ROA RIR databaseRADB, RIPE 672 100% 67
149.134.177.0/24 No ROA RIR databaseRADB, RIPE 672 100% 67
149.134.148.0/24 No ROA RIR databaseRADB, RIPE 671 100% 67
149.134.152.0/24 No ROA RIR databaseRADB, RIPE 671 100% 67
149.134.168.0/24 No ROA RIR databaseRADB, RIPE 671 100% 67
149.134.170.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
149.134.171.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
149.134.172.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
149.134.176.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
149.134.144.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
149.134.145.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
149.134.156.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
149.134.157.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
149.134.158.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
149.134.146.0/24 Valid RIR databaseRADB, RIPE 670 100% 67

AS-SET

AS48075 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 28 are in fix.csv.

  • ROA: none7
  • Route object: RIR1
  • Route object: not announced20
ChangePrefix or setDetailFull-table peers
ROA: none149.134.180.0/24No ROA covers it. Add a ROA for AS48075, maxLength 24.672 of 673
Route object: RIR149.134.180.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none149.134.178.0/24No ROA covers it. Add a ROA for AS48075, maxLength 24.673 of 673
ROA: none149.134.174.0/24No ROA covers it. Add a ROA for AS48075, maxLength 24.672 of 673
ROA: none149.134.177.0/24No ROA covers it. Add a ROA for AS48075, maxLength 24.672 of 673
ROA: none149.134.148.0/24No ROA covers it. Add a ROA for AS48075, maxLength 24.671 of 673
ROA: none149.134.152.0/24No ROA covers it. Add a ROA for AS48075, maxLength 24.671 of 673
ROA: none149.134.168.0/24No ROA covers it. Add a ROA for AS48075, maxLength 24.671 of 673

Route objects not announced

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

149.134.147.0/24RADBNo ROA
149.134.149.0/24RADB, RIPENo ROA
149.134.153.0/24RADB, RIPENo ROA
149.134.154.0/24RIPENo ROA
149.134.155.0/24RIPENo ROA
149.134.173.0/24RIPEInvalid: origin
149.134.175.0/24RIPEInvalid: origin
149.134.179.0/24RIPEInvalid: origin
149.134.181.0/24RIPENo ROA
149.134.182.0/24RIPENo ROA
2a02:13e0::/32RIPENo ROA
2a02:13e0::/48RIPENo ROA
2a02:13e0:1::/48RIPENo ROA
2a02:13e0:2::/48RIPENo ROA
2a02:13e0:20::/48RADB, RIPENo ROA
2a02:13e0:21::/48RIPENo ROA
2a02:13e0:fffd::/48RIPENo ROA
2a02:13e0:fffe::/48RIPENo ROA
2a02:13e0:ffff::/48RIPENo ROA
2a02:13e0:ffff:ff00::/56RIPENo 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.