bgpreport

Network · data from 2026-11-12

AS61919 AR3 Servicos em Tecnologia da Informaca

Registry name: AS61919 - AR3 Servicos EIRELI ME, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS61919, 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.
2804:221c:3e00::/40 Invalid: origin None 41 6%low visibility 23
190.112.205.0/24 Valid Other IRR onlyTC 672 100% 67
190.112.207.0/24 Valid Other IRR onlyRADB, TC 672 100% 67
190.112.206.0/24 Valid Other IRR onlyRADB, TC 671 100% 67
190.112.204.0/24 Valid Other IRR onlyTC 669 99% 67
2804:17d8::/32 Valid Other IRR onlyALTDB, RADB, TC 632 99% 67

AS-SET

PeeringDB's irr_as_set for AS61919: TC::AS61919. 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 (AS61919 isn't in the set, or no route object for AS61919 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 objectsAS61919 in itNot covered
TC::AS61919 A single AS number, not a set: AS61919 (this network), 8 route objects.

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.

  • ROA: origin1
  • Route object: none1
  • Route object: RIR5
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: origin2804:221c:3e00::/40ROAs covering it name AS264592, not AS61919. If AS61919 should announce it, add a ROA for AS61919.41 of 636
Route object: none2804:221c:3e00::/40No route object for it. Add a route object with origin AS61919 in the RIR database for the space.41 of 636
Route object: RIR190.112.205.0/24Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR190.112.207.0/24Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR190.112.206.0/24Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR190.112.204.0/24Route object only in TC. Add it in the RIR database for the space.669 of 673
Route object: RIR2804:17d8::/32Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.632 of 636

Route objects not announced

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

190.112.204.0/22RADB, TCValid
190.112.204.0/23TCValid
190.112.206.0/23TCValid

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.