bgpreport

Network · data from 2026-11-12

AS6315 XMission

Registry name: XMISSION - XMission, L.C., US · PeeringDB

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

Announced routes

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

44.40.48.0/24 No ROA Other IRR onlyRADB 671 100% 68
45.115.61.0/24 No ROA Other IRR onlyRADB 671 100% 68
103.70.38.0/24 No ROA Other IRR onlyRADB 671 100% 68
103.178.164.0/23 No ROA Other IRR onlyRADB 671 100% 68
192.154.7.0/24 No ROA Other IRR onlyRADB 671 100% 68
199.88.179.0/24 No ROA Other IRR onlyRADB 671 100% 68
204.99.129.0/24 No ROA Other IRR onlyRADB 671 100% 68
2606:6680:31::/48 No ROA Other IRR onlyRADB 635 100% 69
2606:6680:32::/48 No ROA Other IRR onlyRADB 635 100% 69
2620:53:2000::/48 No ROA Other IRR onlyRADB 635 100% 69
2607:24c0:2000::/36 Valid Nonecovered by 2607:24c0::/32 635 100% 67
198.60.108.0/24 Valid Other IRR onlyRADB 673 100% 67
198.60.109.0/24 Valid Other IRR onlyRADB 673 100% 67
198.60.110.0/24 Valid Other IRR onlyRADB 673 100% 67
198.60.113.0/24 Valid Other IRR onlyRADB 673 100% 67
198.60.114.0/24 Valid Other IRR onlyRADB 673 100% 67
68.69.160.0/20 Valid Other IRR onlyRADB 671 100% 68
198.60.22.0/24 Valid Other IRR onlyRADB 671 100% 68
198.60.80.0/22 Valid Other IRR onlyRADB 671 100% 68
198.60.84.0/24 Valid Other IRR onlyRADB 671 100% 68
198.60.104.0/22 Valid Other IRR onlyRADB 671 100% 68
198.60.108.0/23 Valid Other IRR onlyRADB 671 100% 68
198.207.196.0/24 Valid Other IRR onlyRADB 671 100% 68
199.104.120.0/21 Valid Other IRR onlyRADB 671 100% 68
204.107.178.0/24 Valid Other IRR onlyRADB 671 100% 68
204.228.128.0/19 Valid Other IRR onlyRADB 671 100% 68
204.228.154.0/24 Valid Other IRR onlyRADB 671 100% 68
204.228.155.0/24 Valid Other IRR onlyRADB 671 100% 68
207.135.128.0/19 Valid Other IRR onlyRADB 671 100% 68
207.135.153.0/24 Valid Other IRR onlyRADB 671 100% 68
207.135.154.0/24 Valid Other IRR onlyRADB 671 100% 68
207.135.155.0/24 Valid Other IRR onlyRADB 671 100% 68
166.70.0.0/16 Valid Other IRR onlyRADB 668 99% 68
2607:24c0::/32 Valid Other IRR onlyRADB 635 100% 69
2607:24c0:3000::/37 Valid Other IRR onlyRADB 635 100% 69
2607:fa18::/32 Valid Other IRR onlyRADB 635 100% 69
2607:24c0:4000::/37 Valid Other IRR onlyRADB 632 99% 69
102.129.219.0/24 Valid RIR databaseAFRINIC, RADB 671 100% 68
185.127.92.0/24 Valid RIR databaseRIPE 671 100% 68

AS-SET

PeeringDB's irr_as_set for AS6315: RADB::AS-XMISSION. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS6315 isn't in the set, or no route object for AS6315 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS6315 in itNot covered
RADB::AS-XMISSION RADB 201105 Yes 0

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

  • ROA: none10
  • Route object: none1
  • Route object: RIR36
  • Route object: not announced16
ChangePrefix or setDetailFull-table peers
ROA: none44.40.48.0/24No ROA covers it. Add a ROA for AS6315, maxLength 24.671 of 673
Route object: RIR44.40.48.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none45.115.61.0/24No ROA covers it. Add a ROA for AS6315, maxLength 24.671 of 673
Route object: RIR45.115.61.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none103.70.38.0/24No ROA covers it. Add a ROA for AS6315, maxLength 24.671 of 673
Route object: RIR103.70.38.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none103.178.164.0/23No ROA covers it. Add a ROA for AS6315, maxLength 23.671 of 673
Route object: RIR103.178.164.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none192.154.7.0/24No ROA covers it. Add a ROA for AS6315, maxLength 24.671 of 673
Route object: RIR192.154.7.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none199.88.179.0/24No ROA covers it. Add a ROA for AS6315, maxLength 24.671 of 673
Route object: RIR199.88.179.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none204.99.129.0/24No ROA covers it. Add a ROA for AS6315, maxLength 24.671 of 673
Route object: RIR204.99.129.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none2606:6680:31::/48No ROA covers it. Add a ROA for AS6315, maxLength 48.635 of 636
Route object: RIR2606:6680:31::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
ROA: none2606:6680:32::/48No ROA covers it. Add a ROA for AS6315, maxLength 48.635 of 636
Route object: RIR2606:6680:32::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
ROA: none2620:53:2000::/48No ROA covers it. Add a ROA for AS6315, maxLength 48.635 of 636
Route object: RIR2620:53:2000::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: none2607:24c0:2000::/36No route object for it. A route object for 2607:24c0::/32 with origin AS6315 covers it (filters allowing more-specifics accept it). Add a route object with origin AS6315 in the RIR database for the space.635 of 636
Route object: RIR198.60.108.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR198.60.109.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR198.60.110.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR198.60.113.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR198.60.114.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR68.69.160.0/20Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR198.60.22.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR198.60.80.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR198.60.84.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR198.60.104.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR198.60.108.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR198.207.196.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR199.104.120.0/21Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR204.107.178.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR204.228.128.0/19Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR204.228.154.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR204.228.155.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR207.135.128.0/19Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR207.135.153.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR207.135.154.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR207.135.155.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR166.70.0.0/16Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR2607:24c0::/32Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2607:24c0:3000::/37Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2607:fa18::/32Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2607:24c0:4000::/37Route object only in RADB. Add it in the RIR database for the space.632 of 636

Route objects not announced

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

44.40.44.0/22RADBNo ROA
44.115.61.0/24RADBNo ROA
104.36.96.0/22RADBNo ROA
104.192.43.0/24RADBNo ROA
162.221.116.0/22RADBNo ROA
192.111.84.0/23RADBNo ROA
193.84.87.0/24RADBNo ROA
199.33.223.0/24RADBNo ROA
199.74.220.0/24RADBNo ROA
208.83.224.0/24RADBNo ROA
2001:470:141::/48ARINValid
2602:fc38::/48RADBNo ROA
2602:fe5d::/36RADBNo ROA
2602:ffba::/36RADBNo ROA
2604:9d40:120::/48ARIN, RADBValid
2607:24c0:1000::/40RADBValid

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.