bgpreport

Network · data from 2026-11-12

AS399888 WireCat

Registry name: WIRECAT-LLC - WireCat LLC, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS399888, 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.32.102.0/24 No ROA Other IRR onlyRADB 671 100% 68
44.30.55.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2
45.45.226.0/24 Valid Nonecovered by 45.45.224.0/22 671 100% 68
208.75.131.0/24 Valid Nonecovered by 208.75.128.0/22 671 100% 68
2602:fc52:30f::/48 Valid Nonecovered by 2602:fc52::/32 634 100% 69
2602:fc52:4823::/48 Valid Nonecovered by 2602:fc52::/32 333 52% 65
2602:fc52:4825::/48 Valid Nonecovered by 2602:fc52::/32 333 52% 65
208.75.128.0/24 Valid Nonecovered by 208.75.128.0/22 115 17% 39
45.45.224.0/24 Valid Other IRR onlyRADB 671 100% 68
45.45.227.0/24 Valid Other IRR onlyRADB 670 100% 67
2602:fc52:100::/40 Valid Other IRR onlyRADB 635 100% 69
2602:fc52:30d::/48 Valid Other IRR onlyRADB 635 100% 69
2602:fc52:357::/48 Valid Other IRR onlyRADB 635 100% 69

AS-SET

PeeringDB's irr_as_set for AS399888: AS399888:AS-ALL. 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 (AS399888 isn't in the set, or no route object for AS399888 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 objectsAS399888 in itNot covered
AS399888:AS-ALL ALTDB 122237 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 18 are in fix.csv.

  • ROA: none2
  • Route object: none6
  • Route object: RIR7
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none44.32.102.0/24No ROA covers it. Add a ROA for AS399888, maxLength 24.671 of 673
Route object: RIR44.32.102.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none44.30.55.0/24No ROA covers it. Add a ROA for AS399888, maxLength 24.2 of 673
Route object: RIR44.30.55.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: none45.45.226.0/24No route object for it. A route object for 45.45.224.0/22 with origin AS399888 covers it (filters allowing more-specifics accept it). Add a route object with origin AS399888 in the RIR database for the space.671 of 673
Route object: none208.75.131.0/24No route object for it. A route object for 208.75.128.0/22 with origin AS399888 covers it (filters allowing more-specifics accept it). Add a route object with origin AS399888 in the RIR database for the space.671 of 673
Route object: none2602:fc52:30f::/48No route object for it. A route object for 2602:fc52::/32 with origin AS399888 covers it (filters allowing more-specifics accept it). Add a route object with origin AS399888 in the RIR database for the space.634 of 636
Route object: none2602:fc52:4823::/48No route object for it. A route object for 2602:fc52::/32 with origin AS399888 covers it (filters allowing more-specifics accept it). Add a route object with origin AS399888 in the RIR database for the space.333 of 636
Route object: none2602:fc52:4825::/48No route object for it. A route object for 2602:fc52::/32 with origin AS399888 covers it (filters allowing more-specifics accept it). Add a route object with origin AS399888 in the RIR database for the space.333 of 636
Route object: none208.75.128.0/24No route object for it. A route object for 208.75.128.0/22 with origin AS399888 covers it (filters allowing more-specifics accept it). Add a route object with origin AS399888 in the RIR database for the space.115 of 673
Route object: RIR45.45.224.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR45.45.227.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR2602:fc52:100::/40Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2602:fc52:30d::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2602:fc52:357::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

45.45.224.0/22ARINValid
208.75.128.0/22ARINValid
2602:fc52::/32ARINValid

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.