bgpreport

Network · data from 2026-11-12

AS61678 NETWAY INFORMATICA

Registry name: AS61678 - NETWAY INFORMATICA LTDA, BR · PeeringDB

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

Announced routes

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

181.191.201.0/24 Valid Nonecovered by 181.191.200.0/22 670 100% 66
181.191.202.0/24 Valid Nonecovered by 181.191.200.0/22 670 100% 66
2804:1cd4:1c01::/48 Valid Nonecovered by 2804:1cd4:1c00::/40 635 100% 67
2804:1cd4:8c00::/40 Valid Nonecovered by 2804:1cd4:8000::/34 635 100% 67
2804:1cd4:8d00::/40 Valid Nonecovered by 2804:1cd4:8000::/34 635 100% 67
2804:1cd4:8e00::/40 Valid Nonecovered by 2804:1cd4:8000::/34 635 100% 67
2804:1cd4:8f00::/40 Valid Nonecovered by 2804:1cd4:8000::/34 635 100% 67
181.191.202.0/23 Valid Nonecovered by 181.191.200.0/22 16 2%low visibility 11
138.122.140.0/24 Valid Nonecovered by 138.122.140.0/23 14 2%low visibility 9
181.191.200.0/23 Valid Nonecovered by 181.191.200.0/22 4 1%low visibility 4
131.108.164.0/23 Valid Other IRR onlyRADB 672 100% 67
138.122.140.0/23 Valid Other IRR onlyRADB 672 100% 66
138.122.142.0/23 Valid Other IRR onlyRADB 672 100% 66
168.90.1.0/24 Valid Other IRR onlyRADB 672 100% 67
168.90.2.0/24 Valid Other IRR onlyRADB 672 100% 67
168.90.3.0/24 Valid Other IRR onlyRADB 672 100% 67
170.246.236.0/22 Valid Other IRR onlyALTDB, RADB 672 100% 66
45.7.12.0/22 Valid Other IRR onlyRADB 671 100% 67
131.108.164.0/22 Valid Other IRR onlyALTDB, RADB 671 100% 66
131.108.166.0/23 Valid Other IRR onlyRADB 671 100% 67
138.122.140.0/22 Valid Other IRR onlyALTDB, RADB 671 100% 66
168.90.0.0/22 Valid Other IRR onlyALTDB, RADB 671 100% 66
168.90.0.0/23 Valid Other IRR onlyRADB 671 100% 66
168.90.2.0/23 Valid Other IRR onlyRADB 671 100% 66
170.246.236.0/23 Valid Other IRR onlyRADB 671 100% 67
170.246.238.0/23 Valid Other IRR onlyRADB 671 100% 67
181.191.200.0/22 Valid Other IRR onlyRADB 671 100% 66
45.7.12.0/23 Valid Other IRR onlyRADB 670 100% 67
45.7.14.0/23 Valid Other IRR onlyRADB 670 100% 67
2804:1cd4::/32 Valid Other IRR onlyALTDB, RADB 635 100% 67
2804:1cd4:1c00::/40 Valid Other IRR onlyRADB 635 100% 67
2804:1cd4:8001::/48 Valid Other IRR onlyRADB 635 100% 67
2804:1cd4:8002::/48 Valid Other IRR onlyRADB 635 100% 67
2804:1cd4:8003::/48 Valid Other IRR onlyRADB 635 100% 67
2804:1cd4:8004::/48 Valid Other IRR onlyRADB 635 100% 67
2804:1cd4:8005::/48 Valid Other IRR onlyRADB 635 100% 67
2804:1cd4:8006::/48 Valid Other IRR onlyRADB 635 100% 67
2804:1cd4:8800::/40 Valid Other IRR onlyRADB 635 100% 67
2804:1cd4:8900::/40 Valid Other IRR onlyRADB 635 100% 67
168.90.0.0/24 Valid Other IRR onlyRADB 126 19% 42
138.122.143.0/24 Valid Other IRR onlyRADB 2 0%low visibility 2

AS-SET

PeeringDB's irr_as_set for AS61678: AS61678: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 (AS61678 isn't in the set, or no route object for AS61678 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 objectsAS61678 in itNot covered
AS61678:AS-ALL RADBlists itself further down2 member sets in no database: AS264262:AS-GLOBAL, AS266486:AS-GLOBAL 125202,319 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 53 are in fix.csv.

  • Route object: none10
  • Route object: RIR31
  • AS-SET: missing member2
  • Route object: not announced10
ChangePrefix or setDetailFull-table peers
Route object: none181.191.201.0/24No route object for it. A route object for 181.191.200.0/22 with origin AS61678 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61678 in the RIR database for the space.670 of 673
Route object: none181.191.202.0/24No route object for it. A route object for 181.191.200.0/22 with origin AS61678 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61678 in the RIR database for the space.670 of 673
Route object: none2804:1cd4:1c01::/48No route object for it. A route object for 2804:1cd4:1c00::/40 with origin AS61678 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61678 in the RIR database for the space.635 of 636
Route object: none2804:1cd4:8c00::/40No route object for it. A route object for 2804:1cd4:8000::/34 with origin AS61678 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61678 in the RIR database for the space.635 of 636
Route object: none2804:1cd4:8d00::/40No route object for it. A route object for 2804:1cd4:8000::/34 with origin AS61678 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61678 in the RIR database for the space.635 of 636
Route object: none2804:1cd4:8e00::/40No route object for it. A route object for 2804:1cd4:8000::/34 with origin AS61678 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61678 in the RIR database for the space.635 of 636
Route object: none2804:1cd4:8f00::/40No route object for it. A route object for 2804:1cd4:8000::/34 with origin AS61678 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61678 in the RIR database for the space.635 of 636
Route object: none181.191.202.0/23No route object for it. A route object for 181.191.200.0/22 with origin AS61678 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61678 in the RIR database for the space.16 of 673
Route object: none138.122.140.0/24No route object for it. A route object for 138.122.140.0/23 with origin AS61678 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61678 in the RIR database for the space.14 of 673
Route object: none181.191.200.0/23No route object for it. A route object for 181.191.200.0/22 with origin AS61678 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61678 in the RIR database for the space.4 of 673
Route object: RIR131.108.164.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR138.122.140.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR138.122.142.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR168.90.1.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR168.90.2.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR168.90.3.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR170.246.236.0/22Route object only in ALTDB, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR45.7.12.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR131.108.164.0/22Route object only in ALTDB, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR131.108.166.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR138.122.140.0/22Route object only in ALTDB, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR168.90.0.0/22Route object only in ALTDB, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR168.90.0.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR168.90.2.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR170.246.236.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR170.246.238.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR181.191.200.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR45.7.12.0/23Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR45.7.14.0/23Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR2804:1cd4::/32Route object only in ALTDB, RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:1cd4:1c00::/40Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:1cd4:8001::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:1cd4:8002::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:1cd4:8003::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:1cd4:8004::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:1cd4:8005::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:1cd4:8006::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:1cd4:8800::/40Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:1cd4:8900::/40Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR168.90.0.0/24Route object only in RADB. Add it in the RIR database for the space.126 of 673
Route object: RIR138.122.143.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
AS-SET: missing memberAS61678:AS-ALLAS61678:AS-ALL (RADB) lists AS264262:AS-GLOBAL; no IRR database read has it.
AS-SET: missing memberAS61678:AS-ALLAS61678:AS-ALL (RADB) lists AS266486:AS-GLOBAL; no IRR database read has it.

Route objects not announced

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

131.108.164.0/24RADBValid
131.108.165.0/24RADBValid
131.108.166.0/24RADBValid
131.108.167.0/24RADBValid
2804:1cd4::/33RADBValid
2804:1cd4::/34RADBValid
2804:1cd4:4000::/34RADBValid
2804:1cd4:8000::/33RADBValid
2804:1cd4:8000::/34RADBValid
2804:1cd4:c000::/34RADBValid

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.