bgpreport

Network · data from 2026-11-12

AS269151 AS269151 - SWAP TELECOM

Registry name: AS269151 - SWAP TELECOM, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS269151, 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.
45.180.228.0/22 Valid Other IRR onlyALTDB 669 99% 67
45.180.228.0/23 Valid Other IRR onlyALTDB 669 99% 67
45.180.230.0/23 Valid Other IRR onlyALTDB 669 99% 67
2804:6030::/32 Valid Other IRR onlyALTDB 635 100% 67
2804:6030::/33 Valid Other IRR onlyALTDB 635 100% 67
2804:6030:8000::/33 Valid Other IRR onlyALTDB 635 100% 67
45.180.228.0/24 Valid Other IRR onlyALTDB 211 31% 56
45.180.229.0/24 Valid Other IRR onlyALTDB 211 31% 56
45.180.230.0/24 Valid Other IRR onlyALTDB 211 31% 56
45.180.231.0/24 Valid Other IRR onlyALTDB 211 31% 56

AS-SET

AS269151 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 10 are in fix.csv.

  • Route object: RIR10
ChangePrefix or setDetailFull-table peers
Route object: RIR45.180.228.0/22Route object only in ALTDB. Add it in the RIR database for the space.669 of 673
Route object: RIR45.180.228.0/23Route object only in ALTDB. Add it in the RIR database for the space.669 of 673
Route object: RIR45.180.230.0/23Route object only in ALTDB. Add it in the RIR database for the space.669 of 673
Route object: RIR2804:6030::/32Route object only in ALTDB. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:6030::/33Route object only in ALTDB. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:6030:8000::/33Route object only in ALTDB. Add it in the RIR database for the space.635 of 636
Route object: RIR45.180.228.0/24Route object only in ALTDB. Add it in the RIR database for the space.211 of 673
Route object: RIR45.180.229.0/24Route object only in ALTDB. Add it in the RIR database for the space.211 of 673
Route object: RIR45.180.230.0/24Route object only in ALTDB. Add it in the RIR database for the space.211 of 673
Route object: RIR45.180.231.0/24Route object only in ALTDB. Add it in the RIR database for the space.211 of 673

Route objects not announced

Every route object with origin AS269151 is announced.

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.