bgpreport

Network · data from 2026-11-12

AS8300 Swisscom Lab

Registry name: Test-AS-Main Swisscom (Schweiz) AG, CH · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS8300, 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.
2a02:1211:e400::/40 Valid None 633 100% 67
2a02:1211:e500::/40 Valid None 633 100% 67
2a02:1211:e600::/40 Valid None 633 100% 67
2a02:1211:e700::/40 Valid None 633 100% 67
193.5.21.0/24 Valid RIR databaseRIPE 671 100% 67
193.5.30.0/24 Valid RIR databaseRIPE 671 100% 67
194.209.74.0/24 Valid RIR databaseRIPE 671 100% 67
194.209.218.0/24 Valid RIR databaseRIPE 671 100% 67
62.202.201.0/24 Valid RIR databaseRIPE 669 99% 67
62.202.203.0/24 Valid RIR databaseRIPE 669 99% 67
2001:918:1ab::/48 Valid RIR databaseRIPE 634 100% 68
2001:918:f00::/40 Valid RIR databaseRIPE 634 100% 68
2001:918:ffb7::/48 Valid RIR databaseRIPE 634 100% 68
193.134.248.0/23 Valid RIR databaseRIPE 2 0%low visibility 2
2001:918:ff74::/48 Valid RIR databaseRIPE 1 0%low visibility 1

AS-SET

AS8300'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 8 are in fix.csv.

  • Route object: none4
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
Route object: none2a02:1211:e400::/40No route object for it. Add a route object with origin AS8300 in the RIR database for the space.633 of 636
Route object: none2a02:1211:e500::/40No route object for it. Add a route object with origin AS8300 in the RIR database for the space.633 of 636
Route object: none2a02:1211:e600::/40No route object for it. Add a route object with origin AS8300 in the RIR database for the space.633 of 636
Route object: none2a02:1211:e700::/40No route object for it. Add a route object with origin AS8300 in the RIR database for the space.633 of 636

Route objects not announced

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

212.243.101.0/24RIPEValid
2001:918:ff73::/48RIPEValid
2001:918:ff76::/48RIPEValid
2001:918:ff77::/48RIPEValid

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.